CVE-2021-20217
CVE-2021-20217 is a high-severity vulnerability in Privoxy with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-617.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- CVSS v2: 7.8
- EPSS exploit prediction: 1% (69th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-617
- Affected product: Privoxy
- Published:
- Last modified:
Description
A flaw was found in Privoxy in versions before 3.0.31. An assertion failure triggered by a crafted CGI request may lead to denial of service. The highest threat from this vulnerability is to system availability.
Frequently asked questions
- What is CVE-2021-20217?
- A flaw was found in Privoxy in versions before 3.0.31. An assertion failure triggered by a crafted CGI request may lead to denial of service. The highest threat from this vulnerability is to system availability.
- How severe is CVE-2021-20217?
- CVE-2021-20217 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2021-20217 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2021-20217?
- CVE-2021-20217 affects Privoxy. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2021-20217?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2021-20217 published?
- CVE-2021-20217 was published on 2021-03-25 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:privoxy:privoxy:*:*:*:*:*:*:*:*
More vulnerabilities in Privoxy
- CVE-2019-3699 — High (CVSS 7.7): UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of privoxy on openSUSE Leap 15.1, Factory allows…
- CVE-2021-44542 — High (CVSS 7.5): A memory leak vulnerability was found in Privoxy when handling errors.
- CVE-2021-44541 — High (CVSS 7.5): A vulnerability was found in Privoxy which was fixed in process_encrypted_request_headers() by freeing header memory…
- CVE-2021-44540 — High (CVSS 7.5): A vulnerability was found in Privoxy which was fixed in get_url_spec_param() by freeing memory of compiled pattern spec…
- CVE-2021-20209 — High (CVSS 7.5): A memory leak vulnerability was found in Privoxy before 3.0.29 in the show-status CGI handler when no action files are…
- CVE-2021-20216 — High (CVSS 7.5): A flaw was found in Privoxy in versions before 3.0.31. A memory leak that occurs when decompression fails unexpectedly…
Other CWE-617 (Reachable Assertion) vulnerabilities
- CVE-2020-3615 — Critical (CVSS 9.8): Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue…
- CVE-2019-9795 — Critical (CVSS 9.8): A vulnerability where type-confusion in the IonMonkey just-in-time (JIT) compiler could potentially be used by…
- CVE-2026-31739 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The…
- CVE-2020-12417 — High (CVSS 8.8): Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in…
- CVE-2020-6623 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_get_index.
- CVE-2020-6619 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek.