Proxy crash via malformed Range header
Published Aug 12, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in Polipo 1.1.1 and earlier allows remote attackers to crash the proxy via a malformed Range header. When NDEBUG removes the server.c range-bound assertion, descending byte bounds continue into processing that writes 10 bytes beyond a 7-byte heap allocation. The proxy port must accept the unauthenticated request; the demonstrated consequence is process termination and service interruption.
Summary
What happened
Heap-based buffer overflow in Polipo 1.1.1 and earlier allows remote attackers to crash the proxy via a malformed Range header. When NDEBUG removes the server.c range-bound assertion, descending byte bounds continue into processing that writes 10 bytes beyond a 7-byte heap allocation. The proxy port must accept the unauthenticated request; the demonstrated consequence is process termination and service interruption.
The record
- CVE
- CVE-2021-38614
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Polipo Project
- Product
- Polipo
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 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=0 <=1.1.1
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
- Malformed Range header denial-of-service proof of conceptproof of concept · demonstrated
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