CVE-2020-35502

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.

CVSS v3 7.5 HIGH
CVSS v2.0 7.8 HIGH

7.5^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

7.8^/10

CVSS v2.0 : HIGH

Vector : AV:N/AC:L/Au:N/C:N/I:N/A:C

Exploitability : 10.0 / Impact : 6.9

Access Vector NETWORK

Access Complexity LOW

Authentication NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact COMPLETE

References

Link	Resource
https://bugzilla.redhat.com/show_bug.cgi?id=1928749	Issue Tracking Third Party Advisory
https://security.gentoo.org/glsa/202107-16	Third Party Advisory
https://www.privoxy.org/3.0.29/user-manual/whatsnew.html	Release Notes Vendor Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=1928749	Issue Tracking Third Party Advisory
https://security.gentoo.org/glsa/202107-16	Third Party Advisory
https://www.privoxy.org/3.0.29/user-manual/whatsnew.html	Release Notes Vendor Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:privoxy:privoxy:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2021-03-25 19:15

Updated : 2024-11-21 05:27

NVD link : CVE-2020-35502

Mitre link : CVE-2020-35502

CVE.ORG link : CVE-2020-35502

JSON object : View

Products Affected

privoxy

privoxy

CWE

CWE-401

Missing Release of Memory after Effective Lifetime

{"id": "CVE-2020-35502", "cveTags": [], "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 7.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:C", "authentication": "NONE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "COMPLETE", "confidentialityImpact": "NONE"}, "acInsufInfo": false, "impactScore": 6.9, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2021-03-25T19:15:12.610", "references": [{"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1928749", "tags": ["Issue Tracking", "Third Party Advisory"], "source": "secalert@redhat.com"}, {"url": "https://security.gentoo.org/glsa/202107-16", "tags": ["Third Party Advisory"], "source": "secalert@redhat.com"}, {"url": "https://www.privoxy.org/3.0.29/user-manual/whatsnew.html", "tags": ["Release Notes", "Vendor Advisory"], "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1928749", "tags": ["Issue Tracking", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.gentoo.org/glsa/202107-16", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.privoxy.org/3.0.29/user-manual/whatsnew.html", "tags": ["Release Notes", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-401"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Se encontr\u00f3 un fallo en Privoxy en versiones anteriores a 3.0.29. Unas p\u00e9rdidas de memoria cuando una respuesta es almacenada en el b\u00fafer y es alcanzado el l\u00edmite del b\u00fafer o Privoxy se est\u00e1 quedando sin memoria pueden conllevar a un bloqueo del sistema"}], "lastModified": "2024-11-21T05:27:26.427", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:privoxy:privoxy:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "0C2D9175-6366-48B3-BE07-97C0C153D2EC", "versionEndExcluding": "3.0.29"}], "operator": "OR"}]}], "sourceIdentifier": "secalert@redhat.com"}