Response smuggling via misparsed Transfer-Encoding list
Published May 22, 2020 · Updated Aug 4, 2024
HTTP response smuggling in Puma 3.12.4 and earlier and 4.0.0 through 4.3.3 allows remote attackers to poison downstream responses. Puma::Client#setup_body treats Transfer-Encoding as chunked only when the entire value equals chunked, so a comma-separated value containing chunked is handled as an unframed body. Unauthenticated network access is sufficient; conflicting message boundaries can inject a response into another client connection.
Summary
What happened
HTTP response smuggling in Puma 3.12.4 and earlier and 4.0.0 through 4.3.3 allows remote attackers to poison downstream responses. Puma::Client#setup_body treats Transfer-Encoding as chunked only when the entire value equals chunked, so a comma-separated value containing chunked is handled as an unframed body. Unauthenticated network access is sufficient; conflicting message boundaries can inject a response into another client connection.
The record
- CVE
- CVE-2020-11076
- Published
- May 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Puma
- Product
- Puma
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.12.5
- Affected versionversion=>= 4.0.0, < 4.3.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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