(DoS) Denial of Service from unchecked request length in conduit-hyper
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-39294
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:40 UTC · Revision 1
Source evidence
(DoS) Denial of Service from unchecked request length in conduit-hyper
core-osv · Original sourcePublished 31 Oct 2022, 00:00 UTC
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.
osv:CVE-2022-39294
Complete source record
{
"id": "186e82711e8268deee3c1900771d8b85cfb12b553afad79dc4191c22f5370936",
"url": "https://osv.dev/vulnerability/CVE-2022-39294",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "(DoS) Denial of Service from unchecked request length in conduit-hyper",
"summary": "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.",
"evidence": "osv:CVE-2022-39294",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2022-39294",
"aliases": [
"CVE-2022-39294",
"GHSA-9398-5ghf-7pr6",
"RUSTSEC-2022-0066"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/conduit-rust/conduit-hyper",
"type": "GIT",
"events": [
{
"introduced": "83cc0dd046bc69bd5963d28565d1f824262d8001"
},
{
"fixed": "ceba64508b4d44cd13578610f02245c0eb7fea70"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0.2.0-alpha.3"
},
{
"fixed": "0.4.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
}
],
"versions": [
"0.2.0-NA",
"v0.4.1",
"v0.4.0",
"v0.3.0",
"v0.3.0-alpha.7",
"v0.3.0-alpha.5",
"v0.3.0-alpha.6",
"v0.3.0-alpha.4",
"v0.3.0-alpha.3",
"v0.3.0-alpha.2",
"v0.3.0-alpha.1",
"v0.3.0-alpha.0",
"v0.2.0",
"v0.2.0-alpha.4",
"v0.2.0-alpha.3"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-39294.json"
}
}
],
"modified": "2026-10-28T02:30:24.321102860Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/39xxx/CVE-2022-39294.json",
"https://github.com/conduit-rust/conduit-hyper/security/advisories/GHSA-9398-5ghf-7pr6",
"https://nvd.nist.gov/vuln/detail/CVE-2022-39294"
],
"provider_metadata": {
"cwe_ids": [
"CWE-400"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/39xxx/CVE-2022-39294.json"
}
},
"related_cves": [
{
"value": "CVE-2022-39294",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490935,
"published_at": "2022-10-31T00:00:00+00:00"
}