High severity · published Mar 25, 2021
CVE-2021-20211
A flaw was found in Privoxy in versions before 3.0.29
7.5
CVSS
2.1%
EPSS
No
On KEV
Description
A flaw was found in Privoxy in versions before 3.0.29. Memory leak when client tags are active can cause a system crash.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)2.1% · higher than 82% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PR
Privoxy · Privoxy
before 3.0.29 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2021-20211
CVE.org
https://www.cve.org/CVERecord?id=CVE-2021-20211
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=1928733
Third Party Advisory
https://security.gentoo.org/glsa/202107-16
Release Notes
https://www.privoxy.org/3.0.29/user-manual/whatsnew.html
More from Privoxy
7.8
CVE-2019-3699
UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of privoxy on openSUSE Leap 15.1, Factory allows local attackers to escalate from user privoxy to root
7.5
CVE-2021-44542
A memory leak vulnerability was found in Privoxy when handling errors
7.5
CVE-2021-44541
A vulnerability was found in Privoxy which was fixed in process_encrypted_request_headers() by freeing header memory when failing to get the request destination
7.5
CVE-2021-44540
A vulnerability was found in Privoxy which was fixed in get_url_spec_param() by freeing memory of compiled pattern spec before bailing
7.5
CVE-2021-20209
A memory leak vulnerability was found in Privoxy before 3.0.29 in the show-status CGI handler when no action files are configured