CVE-2021-32714Critical· 9.1▾ MidnightInteger overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 50.1 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 3.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
1.1%
1.1% → 1.2%
Last analysed / modified upstream
5.9 → 9.1
medium → critical
When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation,
this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.
To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send
requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible,
any upstream proxies must accept a chunk size greater than 64 bits.
hyper >= 0.0.0-0, < 0.14.10Upgrade to a patched release:
hyper 0.14.10Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.