Most recent entries from all

bdu:2024-10889

BREW-icloudpd-CVE-2024-49768 — Waitress has request processing race condition in HTTP pipelining with invalid first request

Affected: Homebrew: icloudpd

### Impact

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.

### Patches

Waitress 3.0.1 fixes the race condition.

### Workarounds

Disable `channel_request_lookahead`, this is set to `0` by default disabling this feature. For this vulnerability this value is required to be changed from the default.

### For more information

If you have any questions or comments about this advisory: * Open an issue in https://github.com/Pylons/waitress/issues (if not sensitive or security related) * email the Pylons Security mailing list: [pylons-project-security@googlegroups.com](mailto:pylons-project-security@googlegroups.com) (if security related)

### Thanks

- m4yfly and urn1ce From TianGong Team of Legendsec at Qi'anxin Group.

EUVD-2026-198349

fkie_cve-2024-49768

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.

GHSA-9298-4cf8-g4wj — Waitress has request processing race condition in HTTP pipelining with invalid first request

Affected: PyPI: waitress

### Impact

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.

### Patches

Waitress 3.0.1 fixes the race condition.

### Workarounds

Disable `channel_request_lookahead`, this is set to `0` by default disabling this feature. For this vulnerability this value is required to be changed from the default.

### For more information

### Thanks

- m4yfly and urn1ce From TianGong Team of Legendsec at Qi'anxin Group.

OESA-2024-2333 — python-waitress security update

Affected: openEuler:22.03-LTS-SP3: python-waitress

Waitress is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.5+. It is also known to run on PyPy 1.6.0+ on UNIX. It supports HTTP/1.0 and HTTP/1.1. Security Fix(es): (CVE-2024-49768)

PYSEC-2024-210

Affected: PyPI: waitress

RHSA-2024:10145 — Red Hat Security Advisory: OpenShift Container Platform 4.15.39 packages and security update

waitress: python-waitress: request processing race condition in HTTP pipelining with invalid first request waitress: Waitress has a denial of service leading to high CPU usage/resource exhaustion

UBUNTU-CVE-2024-49768

Affected: Ubuntu:Pro:24.04:LTS: waitress

WID-SEC-W-2024-3488 — Red Hat OpenShift Container Platform: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service zu verursachen.