Proxy service crash via crafted CGI request
Published Mar 25, 2021 · Updated Aug 3, 2024
Reachable assertion in Privoxy before 3.0.31 allows remote attackers to crash the proxy service via a crafted CGI request. Its CGI request handling permits malformed input to reach an internal assertion, terminating the Privoxy process; the upstream notice does not identify the exact function or input field. No authentication or user interaction is required, and the documented consequence is loss of proxy availability rather than data disclosure or modification.
Summary
What happened
Reachable assertion in Privoxy before 3.0.31 allows remote attackers to crash the proxy service via a crafted CGI request. Its CGI request handling permits malformed input to reach an internal assertion, terminating the Privoxy process; the upstream notice does not identify the exact function or input field. No authentication or user interaction is required, and the documented consequence is loss of proxy availability rather than data disclosure or modification.
The record
- CVE
- CVE-2021-20217
- Published
- Mar 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Privoxy Developers
- Product
- Privoxy
- Classifications
- CWE-617, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=privoxy 3.0.31
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo