GitHub Advisoryadvisory · crates.io

GHSA-9398-5ghf-7pr6 conduit-hyper vulnerable to Denial of Service from unchecked request length

HIGH Published 2022-10-31 Modified 2022-10-31 Official page ↗
Aliases
CVE-2022-39294
Ecosystem
crates.io
Packages
conduit-hyper
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-1284, CWE-400
Reviewed
2022-10-31

Affected packages

• crates.io conduit-hyper: >= 0.2.0-alpha.3, < 0.4.2 → fixed in 0.4.2

Description

Prior to version 0.4.2, `conduit-hyper` did not check any limit on a request's length before calling `hyper::body::to_bytes`. 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, 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. The vulnerability was discovered by Ori Hollander from the JFrog Security Research team.

Related

Alias · CVE (1)

  • CVE-2022-39294 conduit-hyper integrates a conduit application with the hyper server. vulnerability

Weakness · CWE (2)

  • CWE-1284 Improper Validation of Specified Quantity in Input weakness
  • CWE-400 Uncontrolled Resource Consumption weakness

References