mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-07 04:01:35 +01:00
Add advisory for hyper Transfer-Encoding header parsing (#968)
This commit is contained in:
21
crates/hyper/RUSTSEC-0000-0000.md
Normal file
21
crates/hyper/RUSTSEC-0000-0000.md
Normal file
@@ -0,0 +1,21 @@
|
||||
```toml
|
||||
[advisory]
|
||||
id = "RUSTSEC-0000-0000"
|
||||
package = "hyper"
|
||||
date = "2021-07-07"
|
||||
url = "https://github.com/hyperium/hyper/security/advisories/GHSA-5h46-h7hh-c6x9"
|
||||
keywords = ["http", "parsing", "data loss"]
|
||||
aliases = ["CVE-2021-32714", "GHSA-5h46-h7hh-c6x9"]
|
||||
|
||||
[versions]
|
||||
patched = [">= 0.14.10"]
|
||||
```
|
||||
|
||||
# Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss
|
||||
|
||||
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.
|
||||
Reference in New Issue
Block a user