Bug 2322460 (CVE-2024-49768)
| Summary: | CVE-2024-49768 waitress: python-waitress: request processing race condition in HTTP pipelining with invalid first request | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | amctagga, aoconnor, bdettelb, bniver, doconnor, eglynn, flucifre, gmeno, jjoyce, jschluet, lhh, lsvaty, mbenjamin, mburns, mgarciac, mhackett, pgrist, sostapov, teagle, vereddy |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
A flaw was found in the Waitress WSGI server for Python. A remote client can send a request that is exactly `recv_bytes`, which defaults to 8192 long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default), Waitress won't read any more requests, and when the first request fails due to a parsing error, it simply closes 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2322494, 2322488, 2322489, 2322490, 2322491, 2322492, 2322493, 2322495, 2322496, 2324285, 2332106 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2024-10-29 15:01:56 UTC
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2024:9613 https://access.redhat.com/errata/RHSA-2024:9613 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2024:9618 https://access.redhat.com/errata/RHSA-2024:9618 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2024:9623 https://access.redhat.com/errata/RHSA-2024:9623 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2024:10145 https://access.redhat.com/errata/RHSA-2024:10145 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Ironic content for Red Hat OpenShift Container Platform 4.12 Via RHSA-2024:10535 https://access.redhat.com/errata/RHSA-2024:10535 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Ironic content for Red Hat OpenShift Container Platform 4.13 Via RHSA-2024:10815 https://access.redhat.com/errata/RHSA-2024:10815 This issue has been addressed in the following products: Red Hat OpenStack Platform 16.2 Via RHSA-2025:0201 https://access.redhat.com/errata/RHSA-2025:0201 This issue has been addressed in the following products: Red Hat OpenStack Platform 17.1 for RHEL 9 Via RHSA-2025:1191 https://access.redhat.com/errata/RHSA-2025:1191 This issue has been addressed in the following products: Red Hat OpenStack Platform 17.1 for RHEL 8 Via RHSA-2025:1192 https://access.redhat.com/errata/RHSA-2025:1192 |