conduit-hyper integrates a conduit application with the hyper server. Prior to version 0.4.2, `conduit-hyper` did not check any limit on a request's length before calling [`hyper::body::to_bytes`](https://docs.rs/hyper/latest/hyper/body/fn.to_bytes.html). An attacker could send a malicious request with an abnormally large `Content-Length`, which could lead to a panic if memory allocation failed for that request. In version 0.4.2, `conduit-hyper` sets an internal limit of 128 MiB per request, otherwise returning status 400 ("Bad Request"). This crate is part of the implementation of Rust's [crates.io](https://crates.io/), but that service is not affected due to its existing cloud infrastructure, which already drops such malicious requests. Even with the new limit in place, `conduit-hyper` is not recommended for production use, nor to directly serve the public Internet.
References
Link | Resource |
---|---|
https://github.com/conduit-rust/conduit-hyper/security/advisories/GHSA-9398-5ghf-7pr6 | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
11 Jul 2023, 20:51
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-1284 |
Information
Published : 2022-10-31 19:15
Updated : 2024-02-28 19:29
NVD link : CVE-2022-39294
Mitre link : CVE-2022-39294
CVE.ORG link : CVE-2022-39294
JSON object : View
Products Affected
conduit-hyper_project
- conduit-hyper