Service interruption via unreleased show-status allocation
Published May 25, 2021 · Updated Aug 3, 2024
Memory leak in Privoxy before 3.0.29 allows remote attackers to exhaust service memory through the show-status CGI endpoint. The cgi_show_status no-action-files branch leaves its allocated status string unreleased after mapping the empty-list response. An attacker must reach the CGI interface on an instance with no action files configured; repeated requests can exhaust memory and interrupt service.
Summary
What happened
Memory leak in Privoxy before 3.0.29 allows remote attackers to exhaust service memory through the show-status CGI endpoint. The cgi_show_status no-action-files branch leaves its allocated status string unreleased after mapping the empty-list response. An attacker must reach the CGI interface on an instance with no action files configured; repeated requests can exhaust memory and interrupt service.
The record
- CVE
- CVE-2021-20209
- Published
- May 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Privoxy Developers
- Product
- Privoxy
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 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=before 3.0.29
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