Advisory

GHSA-9398-5ghf-7pr6

Also known as: CVE-2022-39294, RUSTSEC-2022-0066

Summary

conduit-hyper vulnerable to Denial of Service from unchecked request length

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-10-31 18:44 UTC
Modified
2023-11-08 04:10 UTC

Affected packages and fixes

conduit-hyper

crates.io · All systems

Affected

  • introduced 0.2.0-alpha.3, fixed 0.4.2 (semver)

Fixed versions

0.4.2

Fix

  • Fixed version 0.4.2
    cargo update -p conduit-hyper --precise 0.4.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences