Server crash via unchecked URI receive loop
Published Dec 25, 2023 · Updated Apr 23, 2025
Buffer overflow in MicroHttpServer through a8ab029 allows remote attackers to crash the server via an HTTP request with a long URI. The _ParseHeader URI loop passes successive req_buf addresses to recv without enforcing the buffer boundary, causing a one-byte write beyond the global buffer. Access to the listening HTTP service is sufficient, requires no authentication or user interaction, and the demonstrated consequence is process termination.
Summary
What happened
Buffer overflow in MicroHttpServer through a8ab029 allows remote attackers to crash the server via an HTTP request with a long URI. The _ParseHeader URI loop passes successive req_buf addresses to recv without enforcing the buffer boundary, causing a one-byte write beyond the global buffer. Access to the listening HTTP service is sufficient, requires no authentication or user interaction, and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2023-51771
- Published
- Dec 25, 2023
- Updated
- Apr 23, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 25, 2023CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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.
Weakness, pattern, technique
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