Vulnerability CriticalRUSTSEC-2020-0008 · hyper
RUSTSEC-2020-0008: Flaw in hyper allows request smuggling by sending a body in GET requests
Short answerA security vulnerability in the hyper crate: Flaw in hyper allows request smuggling by sending a body in GET requests. Critical severity (CVSS 9.8). Fixed in 0.12.34: update to a fixed version.
| Crate | hyper |
|---|---|
| Type | Vulnerability (format-injection) |
| Affected versions | From 0.11.0 before 0.12.34. |
| Fixed in | 0.12.34 |
| Severity | Critical, CVSS 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-03-19 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35863, GHSA-h3qr-rq2j-74w4 |
What to do
- See which version you have:
cargo tree -i hyper(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p hyper. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplehyper = "0.12.34") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Vulnerable versions of hyper allow GET requests to have bodies, even if there is no Transfer-Encoding or Content-Length header. As per the HTTP 1.1 specification, such requests do not have bodies, so the body will be interpreted as a separate HTTP request.
This allows an attacker who can control the body and method of an HTTP request made by hyper to inject a request with headers that would not otherwise be allowed, as demonstrated by sending a malformed HTTP request from a Substrate runtime. This allows bypassing CORS restrictions. In combination with other vulnerabilities, such as an exploitable web server listening on loopback, it may allow remote code execution.
The flaw was corrected in hyper version 0.12.34.
References
- Package: crates.io/crates/hyper
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0008.html
- Report: github.com/hyperium/hyper/issues/1925
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for hyper
- Vulnerability MediumRUSTSEC-2016-0002 · 2016-05-09HTTPS MitM vulnerability due to lack of hostname verification
- Vulnerability MediumRUSTSEC-2017-0002 · 2017-01-23headers containing newline characters can split messages
- Vulnerability HighRUSTSEC-2021-0020 · 2021-02-05Multiple Transfer-Encoding headers misinterprets request payload
- Vulnerability MediumRUSTSEC-2021-0078 · 2021-07-07Lenient `hyper` header parsing of `Content-Length` could allow request smuggling
- Vulnerability CriticalRUSTSEC-2021-0079 · 2021-07-07Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss
- UnsoundRUSTSEC-2022-0022 · 2022-05-10Parser creates invalid uninitialized value
Up next
Same cratehyper: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?