Conduit Hyper
Approved changes feed: RSS · Atom
cpe:2.3:a:conduit-rust:conduit-hyper:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Conduit Rust (fb0f353f-2ca0-518c-8a0a-6b2ce85cf1d5) |
|---|---|
| Product | Conduit Hyper (e358bc3c-c2e0-5c0a-95ac-12c3be7a5fe7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-39294 |
vulnerable | 2026-06-08 05:47:18.545309 |
(DoS) Denial of Service from unchecked request length in conduit-hyper
HIGH (7.5)
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.
Published: 2022-10-31T00:00:00.000Z
Updated: 2025-04-23T16:42:04.247Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.