Request smuggling via lookahead closure race
Published Oct 29, 2024 · Updated Oct 29, 2024
HTTP request smuggling in Pylons Project Waitress 2.0.0 through 3.0.0 allows remote attackers to process a pipelined request. With channel_request_lookahead enabled, HTTPChannel.received accepts a second request after the service thread flags an invalid first request for closure. The nondefault setting and an initial request exactly matching recv_bytes are required; the worker then services a request that the closing connection should discard.
Summary
What happened
HTTP request smuggling in Pylons Project Waitress 2.0.0 through 3.0.0 allows remote attackers to process a pipelined request. With channel_request_lookahead enabled, HTTPChannel.received accepts a second request after the service thread flags an invalid first request for closure. The nondefault setting and an initial request exactly matching recv_bytes are required; the worker then services a request that the closing connection should discard.
The record
- CVE
- CVE-2024-49768
- Published
- Oct 29, 2024
- Updated
- Oct 29, 2024
- Vendor
- Pylons Project
- Product
- Waitress
- Classifications
- CWE-444, CWE-367, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Oct 29, 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=>= 2.0.0, < 3.0.1
- Affected versionversion=2.0.0 <3.0.1
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