Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in waitress
CVE-2024-49768
- waitress
Summary
Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly "recv_bytes" (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection. However, when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed. This issue affects waitress versions 2.0.0b0 through 3.0.0. As a workaround, disable "channel_request_lookahead", this is set to "0" by default disabling this feature.
- LOW
- NETWORK
- HIGH
- UNCHANGED
- NONE
- NONE
- HIGH
- NONE
CWE-444 - HTTP Request Smuggling
Entities such as web servers, web caching proxies, and application firewalls could parse HTTP requests differently. When there are two or more such entities in the path of an HTTP request, an attacker can send a specially crafted HTTP request that is seen as two different sets of requests by the attacked devices, allowing the attacker to smuggle a request into one device without the other device being aware of it. Such a vulnerability can prove devastating, for it enables further attacks on the application, like web cache poisoning, session hijacking, cross-site scripting, security bypassing, and sensitive information exposure.
References
Advisory Timeline
- Published
