Server crash via unchecked request length
Published Oct 31, 2022 · Updated Apr 23, 2025
Denial of service in conduit-hyper before 0.4.2 allows remote attackers to crash the server process via an oversized Content-Length header. The request path passes the declared body size to hyper::body::to_bytes without a limit, which can trigger a failed allocation and panic. The application must expose the embedded server without an upstream request-size limit; successful exploitation interrupts the hosting process.
Summary
What happened
Denial of service in conduit-hyper before 0.4.2 allows remote attackers to crash the server process via an oversized Content-Length header. The request path passes the declared body size to hyper::body::to_bytes without a limit, which can trigger a failed allocation and panic. The application must expose the embedded server without an upstream request-size limit; successful exploitation interrupts the hosting process.
The record
- CVE
- CVE-2022-39294
- Published
- Oct 31, 2022
- Updated
- Apr 23, 2025
- Vendor
- conduit-rust
- Product
- conduit-hyper
- Classifications
- CWE-400, CWE-1284, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.2.0-alpha.3, < 0.4.2
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