icon

We found results for “

CVE-2022-39294

Date: October 30, 2022

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.

Language: RUST

Severity Score

Severity Score

Weakness Type (CWE)

Uncontrolled Resource Consumption

CWE-400

Improper Validation of Specified Quantity in Input

CWE-1284

CVSS v3.1

Base Score:
Attack Vector (AV): NETWORK
Attack Complexity (AC): LOW
Privileges Required (PR): NONE
User Interaction (UI): NONE
Scope (S): UNCHANGED
Confidentiality (C): NONE
Integrity (I): NONE
Availability (A): HIGH

Do you need more information?

Contact Us