Bug 2322461 (CVE-2024-49769)
| Summary: | CVE-2024-49769 waitress: Waitress has a denial of service leading to high CPU usage/resource exhaustion | ||
|---|---|---|---|
| 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, riramos, 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. When a remote client closes the connection before waitress has had the opportunity to call `getpeername()`, waitress will incorrectly clean up the connection, leading to the main thread attempting to write to a socket that no longer exists, and that socket is not removed from the list of sockets to attempt to process. This leads to a busy-loop calling the write function. A remote attacker could exhaust the available sockets with very little resources required.
|
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: | 2322470, 2322471, 2322476, 2322469, 2322472, 2322473, 2322474, 2322475, 2322477, 2322478, 2322481, 2324286, 2332105, 2350664, 2350665, 2350666 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2024-10-29 15:01:58 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 |