-
Notifications
You must be signed in to change notification settings - Fork 377
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add advisory for hyper Content-Length header parsing (#967)
- Loading branch information
1 parent
a81783c
commit 0148dea
Showing
1 changed file
with
20 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. |