Service interruption via unreleased request buffers
Published Dec 23, 2021 · Updated Aug 4, 2024
Memory leak in send_http_request() in Privoxy before 3.0.33 allows remote attackers to exhaust memory through forwarding errors. Error-return paths in the function omit cleanup of allocated request data, so repeated failed forwarding operations accumulate memory. No authentication or user interaction is required; sustained requests that force forwarding errors can exhaust process memory and interrupt the proxy service.
Summary
What happened
Memory leak in send_http_request() in Privoxy before 3.0.33 allows remote attackers to exhaust memory through forwarding errors. Error-return paths in the function omit cleanup of allocated request data, so repeated failed forwarding operations accumulate memory. No authentication or user interaction is required; sustained requests that force forwarding errors can exhaust process memory and interrupt the proxy service.
The record
- CVE
- CVE-2021-44542
- Published
- Dec 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Privoxy Developers
- Product
- Privoxy
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.33
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