Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 Dec 2020 21:05:31 -0500
From: Jeffrey Walton <>
Subject: Re: CVE request experience (was: Multiple memory leaks
 fixed in Privoxy 3.0.29 stable)

On Wed, Dec 23, 2020 at 12:21 PM Fabian Keil
<> wrote:
> Fabian Keil <> wrote on 2020-11-29:
> >                Announcing Privoxy 3.0.29 stable
> [...]
> > - Security/Reliability:
> >   - Fixed memory leaks when a response is buffered and the buffer
> >     limit is reached or Privoxy is running out of memory.
> >     Commits bbd53f1010b and 4490d451f9b. OVE-20201118-0001.
> I tried to get a CVE for OVE-20201118-0001 by using the
> "new" form at on 2020-11-18 but
> was told by MITRE that "the reported vulnerabilities would
> fall in the scope of Red Hat for assignment" and that their
> mail should be forwarded to
> ...

Related, you are not alone. I just tried to use the form at to get a CVE for a memory error.

That form is impossible to use. I emailed and asked for
the assignment.


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.