GCVE - cpe:2.3:a:conduit-hyper_project:conduit-hyper:0.2.0:alpha4:*:*:*:rust:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:conduit-hyper_project:conduit-hyper:0.2.0:alpha4:*:*:*:rust:*:*

part: a version: 0.2.0 update: alpha4

Vendor	Conduit Hyper Project (`8d1c99ef-a7aa-5f6c-9dd1-aebf9d2dcdd0`)
Product	Conduit Hyper (`9f843368-b995-546f-90a8-69c1aa6478f8`)
Edition	*
Language	*
Software edition	*
Target software	rust
Target hardware	*
Other	*

Notes

Imported from NVD CPE 2.0 feed

PURL	Source	Last updated
`pkg:github/conduit-rust/conduit-hyper`	purl2cpe	2026-06-01 10:17:55.145134

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2022-39294`	vulnerable	2026-06-08 05:47:18.548343	(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 Open on db.gcve.eu Reference links https://github.com/conduit-rust/conduit-hyper/security/advisories/GHSA-9398-5ghf-7pr6	Imported from gcve-enriched-dumps CVE data

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.