hyper
Affected
- introduced
0, fixed0.14.10(semver)
Fixed versions
0.14.10
Fix
- Fixed version
0.14.10cargo update -p hyper --precise 0.14.10
Advisory
Also known as: CVE-2021-32714, RUSTSEC-2021-0079
Integer Overflow in Chunked Transfer-Encoding
Summary
hyper's HTTP server and client code had a flaw that could trigger an integer overflow when decoding chunk sizes that are too big. This allows possible data loss, or if combined with an upstream HTTP proxy that allows chunk sizes larger than hyper does, can result in "request smuggling" or "desync attacks".
Vulnerability
Example:
GET / HTTP/1.1
Host: example.com
Transfer-Encoding: chunked
f0000000000000003
abc
0
hyper only reads the rightmost 64-bit integer as the chunk size. So it reads f0000000000000003 as 3. A loss of data can occur since hyper would then read only 3 bytes of the body. Additionally, an HTTP request smuggling vulnerability would occur if using a proxy which instead has prefix truncation in the chunk size, or that understands larger than 64-bit chunk sizes.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
Impact
To determine if vulnerable to _data loss_, these things must be true:
To determine if vulnerable to _desync attacks_, these things must be true:
Patches
We have released the following patch versions:
Workarounds
Besides upgrading hyper, you can take the following options:
Transfer-Encoding header.Transfer-Encoding chunk sizes greater than what fits in 64-bit unsigned integers.Credits
This issue was initially reported by Mattias Grenfeldt and Asta Olofsson.
Medium Basis: The source's own band: MODERATE
0, fixed 0.14.10 (semver)0.14.10
0.14.10cargo update -p hyper --precise 0.14.10Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0