Denial of service via socket cleanup race
Published Oct 29, 2024 · Updated Nov 17, 2024
Denial of service in Pylons Project Waitress before 3.0.1 allows remote attackers to exhaust sockets and CPU via rapid disconnects. During HTTPChannel construction, wasyncore treats a socket closed before getpeername() as disconnected but leaves its dispatcher registered for writes. An unauthenticated network client needs only to connect and close at the race point; repeated triggers can pin the main thread and consume the socket pool.
Summary
What happened
Denial of service in Pylons Project Waitress before 3.0.1 allows remote attackers to exhaust sockets and CPU via rapid disconnects. During HTTPChannel construction, wasyncore treats a socket closed before getpeername() as disconnected but leaves its dispatcher registered for writes. An unauthenticated network client needs only to connect and close at the race point; repeated triggers can pin the main thread and consume the socket pool.
The record
- CVE
- CVE-2024-49769
- Published
- Oct 29, 2024
- Updated
- Nov 17, 2024
- Vendor
- Pylons Project
- Product
- Waitress
- Classifications
- CWE-772, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Nov 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0.1
- Affected versionversion=< 3.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo