Vulnerability MediumRUSTSEC-2017-0002 · hyper
RUSTSEC-2017-0002: headers containing newline characters can split messages
Short answerA security vulnerability in the hyper crate: headers containing newline characters can split messages. Medium severity (CVSS 5.3). Fixed in 0.10.2, 0.9.18: update to a fixed version.
| Crate | hyper |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.9.18; from 0.10.0 before 0.10.2. |
| Fixed in | 0.10.2, 0.9.18 |
| Severity | Medium, CVSS 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| Published | 2017-01-23 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2017-18587, GHSA-q89x-f52w-6hj2 |
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.9.18") 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
Serializing of headers to the socket did not filter the values for newline bytes (\r or \n), which allowed for header values to split a request or response. People would not likely include newlines in the headers in their own applications, so the way for most people to exploit this is if an application constructs headers based on unsanitized user input.
This issue was fixed by replacing all newline characters with a space during serialization of a header value.
References
- Package: crates.io/crates/hyper
- Advisory: rustsec.org/advisories/RUSTSEC-2017-0002.html
- Web: github.com/hyperium/hyper/wiki/Security-001
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 CriticalRUSTSEC-2020-0008 · 2020-03-19Flaw in hyper allows request smuggling by sending a body in GET requests
- 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?