Request smuggling via undrained request bodies
Published May 24, 2022 · Updated Aug 3, 2024
HTTP request smuggling in Pallets Werkzeug 2.1.0 and earlier allows remote attackers to inject a second request through one request body. Python's HTTP server leaves unread body bytes on the persistent connection, so it parses them as the next request when an application does not consume the body. The disputed behavior requires development mode, HTTP/1.1 keep-alive, an unread body, and an HTTP server outside Werkzeug; the injected request can bypass front-end interpretation.
Summary
What happened
HTTP request smuggling in Pallets Werkzeug 2.1.0 and earlier allows remote attackers to inject a second request through one request body. Python's HTTP server leaves unread body bytes on the persistent connection, so it parses them as the next request when an application does not consume the body. The disputed behavior requires development mode, HTTP/1.1 keep-alive, an unread body, and an HTTP server outside Werkzeug; the injected request can bypass front-end interpretation.
The record
- CVE
- CVE-2022-29361
- Published
- May 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2022CVE 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?
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
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