Server crash via freed epoll context write
Published Dec 30, 2023 · Updated Sep 9, 2024
Use-after-free in ehttp 1.0.6 before 17405b9 allows remote attackers to crash an HTTP server via rapid connections. In read_func, a worker writes CONTEXT_READ_OVER through an EpollContext pointer after a concurrent writable-event path frees the object. No authentication is required; sustained rapid connections reproduce a server crash after roughly 30–60 seconds.
Summary
What happened
Use-after-free in ehttp 1.0.6 before 17405b9 allows remote attackers to crash an HTTP server via rapid connections. In read_func, a worker writes CONTEXT_READ_OVER through an EpollContext pointer after a concurrent writable-event path frees the object. No authentication is required; sustained rapid connections reproduce a server crash after roughly 30–60 seconds.
The record
- CVE
- CVE-2023-52266
- Published
- Dec 30, 2023
- Updated
- Sep 9, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2023CVE publishedPublication date reported by the CVE source.
- Sep 9, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Rapid-connection server crash reproducerfunctional · demonstrated
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