oss-sec mailing list archives
Re: CVE request experience (was: Multiple memory leaks fixed in Privoxy 3.0.29 stable)
From: Jeffrey Walton <noloader () gmail com>
Date: Thu, 24 Dec 2020 21:05:31 -0500
On Wed, Dec 23, 2020 at 12:21 PM Fabian Keil <freebsd-listen () fabiankeil de> wrote:
Fabian Keil <freebsd-listen () fabiankeil de> 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 https://cveform.mitre.org/ 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 secalert () redhat com. ...
Related, you are not alone. I just tried to use the form at https://cveform.mitre.org/ to get a CVE for a memory error. That form is impossible to use. I emailed cve () mitre org and asked for the assignment. Jeff
Current thread:
- Multiple memory leaks fixed in Privoxy 3.0.29 stable Fabian Keil (Nov 29)
- CVE request experience (was: Multiple memory leaks fixed in Privoxy 3.0.29 stable) Fabian Keil (Dec 23)
- Re: CVE request experience (was: Multiple memory leaks fixed in Privoxy 3.0.29 stable) Nick Tait (Dec 23)
- Re: CVE request experience (was: Multiple memory leaks fixed in Privoxy 3.0.29 stable) Jeffrey Walton (Dec 25)
- CVE request experience (was: Multiple memory leaks fixed in Privoxy 3.0.29 stable) Fabian Keil (Dec 23)