CVE-2020-35502

Description

A flaw was found in Privoxy in versions before 3.0.29. Memory leaks when a response is buffered and the buffer limit is reached or Privoxy is running out of memory can lead to a system crash.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.64%
Vendor Advisory gentoo.org Vendor Advisory privoxy.org
Affected: n/a privoxy
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1928749 third party advisory issue tracking
https://www.privoxy.org/3.0.29/user-manual/whatsnew.html release notes vendor advisory
https://security.gentoo.org/glsa/202107-16 third party advisory vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-35502?
CVE-2020-35502 has been scored as a high severity vulnerability.
How to fix CVE-2020-35502?
To fix CVE-2020-35502, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-35502 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-35502 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-35502?
CVE-2020-35502 affects n/a privoxy.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.