mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2025-12-30 00:03:57 +01:00
Add advisory for hyper Content-Length header parsing (#967)
This commit is contained in:
20
crates/hyper/RUSTSEC-0000-0000.md
Normal file
20
crates/hyper/RUSTSEC-0000-0000.md
Normal file
@@ -0,0 +1,20 @@
|
||||
```toml
|
||||
[advisory]
|
||||
id = "RUSTSEC-0000-0000"
|
||||
package = "hyper"
|
||||
date = "2021-07-07"
|
||||
url = "https://github.com/hyperium/hyper/security/advisories/GHSA-f3pg-qwvg-p99c"
|
||||
keywords = ["parsing", "http"]
|
||||
aliases = ["CVE-2021-32715", "GHSA-f3pg-qwvg-p99c"]
|
||||
|
||||
[versions]
|
||||
patched = [">= 0.14.10"]
|
||||
```
|
||||
|
||||
# Lenient `hyper` header parsing of `Content-Length` could allow request smuggling
|
||||
|
||||
`hyper`'s HTTP header parser accepted, according to RFC 7230, illegal contents inside `Content-Length` headers.
|
||||
Due to this, upstream HTTP proxies that ignore the the header may still forward them along if it chooses to ignore the error.
|
||||
|
||||
To be vulnerable, `hyper` must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents
|
||||
but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerablity is unlikely.
|
||||
Reference in New Issue
Block a user