Unauthenticated memory exhaustion via decompression leak
Published Mar 25, 2021 · Updated Aug 3, 2024
Denial-of-service in Privoxy before 3.0.31 allows remote attackers to interrupt proxy service via crafted compressed responses. Its decompression error path leaks allocated memory instead of releasing it when decompression fails unexpectedly. Repeated malformed responses can exhaust the Privoxy process memory and cause a service interruption without authentication or user interaction.
Summary
What happened
Denial-of-service in Privoxy before 3.0.31 allows remote attackers to interrupt proxy service via crafted compressed responses. Its decompression error path leaks allocated memory instead of releasing it when decompression fails unexpectedly. Repeated malformed responses can exhaust the Privoxy process memory and cause a service interruption without authentication or user interaction.
The record
- CVE
- CVE-2021-20216
- Published
- Mar 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Privoxy Developers
- Product
- Privoxy
- Classifications
- CWE-400, CWE-401, T1499
- 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.
Weakness, pattern, technique
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