Unauthenticated service crash via stale buffer pointer
Published Jan 5, 2024 · Updated Sep 4, 2024
Use-after-free in Lotos WebServer 0.1.1 and earlier allows remote attackers to crash the service via an oversized HTTP request URI. buffer_cat can move its allocation with realloc without propagating the returned pointer, so buffer_avail later reads the freed buffer object. A single unauthenticated network request with a 20,000-byte URI reaches the fault, and the published proof of concept demonstrates process termination under AddressSanitizer.
Summary
What happened
Use-after-free in Lotos WebServer 0.1.1 and earlier allows remote attackers to crash the service via an oversized HTTP request URI. buffer_cat can move its allocation with realloc without propagating the returned pointer, so buffer_avail later reads the freed buffer object. A single unauthenticated network request with a 20,000-byte URI reaches the fault, and the published proof of concept demonstrates process termination under AddressSanitizer.
The record
- CVE
- CVE-2024-22088
- Published
- Jan 5, 2024
- Updated
- Sep 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2024CVE publishedPublication date reported by the CVE source.
- Sep 4, 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
- Long-URI Python proof of conceptproof of concept · 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