Logo
componentpython3-waitress
Name
python3-waitress
Version
2.1.2
Type
library
Description
A WSGI server for Python
Licenses
ZPL-2.1
PURL
-
CPE
cpe:2.3:*:*:python3-waitress:2.1.2:*:*:*:*:*:*:*

Other Versions#


Project
Branch
Version
master
3.0.2
scarthgap
3.0.2

Patches#


#
Title
Author
Resolve
1
Assume socket is not connected when passed to
Delta Regeer <bertjw@regeer.org>
CVE-2024-49769
2
Remove test for getpeername()
Delta Regeer <bertjw@regeer.org>
CVE-2024-49769
3
Add documentation for channel_request_lookahead
Delta Regeer <bertjw@regeer.org>
CVE-2024-49768
4
Make DummySock() look more like an actual socket
Delta Regeer <bertjw@regeer.org>
CVE-2024-49768
5
When closing the socket, set it to None
Delta Regeer <bertjw@regeer.org>
CVE-2024-49769
6
Fix a race condition on recv_bytes boundary when request is
Delta Regeer <bertjw@regeer.org>
CVE-2024-49768
7
Remove code not used by waitress from vendored asyncore
Delta Regeer <bertjw@regeer.org>
CVE-2024-49769
8
Add a new test to validate the lookahead race condition
Delta Regeer <bertjw@regeer.org>
CVE-2024-49768
9
Don't exit handle_write early -- even if socket is not
Delta Regeer <bertjw@regeer.org>
CVE-2024-49769
10
HTTPChannel is always created from accept, explicitly set
Delta Regeer <bertjw@regeer.org>
CVE-2024-49769

Vulnerabilities#


Name
Analysis
Description
Patched
Waitress is a Web Server Gateway Interface server for Python 2 and 3. When a remote client closes the connection before waitress has had the opportunity to call getpeername() waitress won't correctly clean up the connection leading to the main thread attempting to write to a socket that no longer exists, but not removing it from the list of sockets to attempt to process. This leads to a busy-loop calling the write function. A remote attacker could run waitress out of available sockets with very little resources required. Waitress 3.0.1 contains fixes that remove the race condition.
Patched
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. Waitress 3.0.1 fixes the race condition. As a workaround, disable channel_request_lookahead, this is set to 0 by default disabling this feature.