OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2026-01-05 11:10:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

Assigned RUSTSEC-2021-0078 to hyper (#972)

Browse Source 
Co-authored-by: tarcieri <tarcieri@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
2021-08-08 12:39:12 -07:00
committed by GitHub
parent 0148dead3a
commit 255194ae7a
2 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.duplicate-id-guard
View File

@@ -1,3 +1,3 @@
This file causes merge conflicts if two ID assignment jobs run concurrently.
This prevents duplicate ID assignment due to a race between those jobs.
bd246e1f4b34100531c2fa8edeff29e12391cca115de6b424aed2a2127e93b03 -
8774b8ca3f52e5e81096af4b1102d97953873237a02fcda2b894a4980646b5db -

40
crates/hyper/RUSTSEC-0000-0000.md → crates/hyper/RUSTSEC-2021-0078.md
View File

@@ -1,20 +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.
```toml
[advisory]
id = "RUSTSEC-2021-0078"
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.