Remote proxy crash via leaked status buffer
Published Mar 25, 2021 · Updated Aug 3, 2024
Memory leak in the show-status CGI handler in Privoxy before 3.0.29 allows remote attackers to crash the proxy via CGI requests. The cgi_show_status function leaves its temporary status string allocated when the configured filter-file list is empty instead of freeing it. Repeated unauthenticated requests must reach Privoxy's internal CGI while no filter files are configured, exhausting memory and stopping the service.
Summary
What happened
Memory leak in the show-status CGI handler in Privoxy before 3.0.29 allows remote attackers to crash the proxy via CGI requests. The cgi_show_status function leaves its temporary status string allocated when the configured filter-file list is empty instead of freeing it. Repeated unauthenticated requests must reach Privoxy's internal CGI while no filter files are configured, exhausting memory and stopping the service.
The record
- CVE
- CVE-2021-20210
- Published
- Mar 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Privoxy Developers
- Product
- Privoxy
- Classifications
- 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.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