CVE-2022-39294
Summary
| CVE | CVE-2022-39294 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-10-31 19:15:00 UTC |
| Updated | 2023-07-11 20:51:00 UTC |
| Description | 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. |
Risk And Classification
Problem Types: CWE-1284
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Conduit-hyper Project | Conduit-hyper | All | All | All | All |
| Application | Conduit-hyper Project | Conduit-hyper | 0.2.0 | - | All | All |
| Application | Conduit-hyper Project | Conduit-hyper | 0.2.0 | alpha3 | All | All |
| Application | Conduit-hyper Project | Conduit-hyper | 0.2.0 | alpha4 | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Denial of Service from unchecked request length · Advisory · conduit-rust/conduit-hyper · GitHub | CONFIRM | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.