Cache poisoning via malformed Content-Length prefixes
Published Jun 30, 2020 · Updated Aug 4, 2024
HTTP request smuggling in Squid before 4.12 and 5.x before 5.0.3 allows remote authenticated users to poison its HTTP cache. ContentLengthInterpreter passes signed or non-OWS-prefixed Content-Length values to numeric parsing instead of rejecting the invalid prefixes. The user must be a trusted proxy client, and an upstream server must interpret the smuggled request and generate the poison response sequence.
Summary
What happened
HTTP request smuggling in Squid before 4.12 and 5.x before 5.0.3 allows remote authenticated users to poison its HTTP cache. ContentLengthInterpreter passes signed or non-OWS-prefixed Content-Length values to numeric parsing instead of rejecting the invalid prefixes. The user must be a trusted proxy client, and an upstream server must interpret the smuggled request and generate the poison response sequence.
The record
- CVE
- CVE-2020-15049
- Published
- Jun 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2020CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- HTTP Request Smuggling in 2020 New Variants New Defenses and New Challengesproof 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