From 255194ae7ae7d5ae8109237d5c836cffe4a6adec Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sun, 8 Aug 2021 12:39:12 -0700 Subject: [PATCH] Assigned RUSTSEC-2021-0078 to hyper (#972) Co-authored-by: tarcieri --- .duplicate-id-guard | 2 +- ...TSEC-0000-0000.md => RUSTSEC-2021-0078.md} | 40 +++++++++---------- 2 files changed, 21 insertions(+), 21 deletions(-) rename crates/hyper/{RUSTSEC-0000-0000.md => RUSTSEC-2021-0078.md} (94%) diff --git a/.duplicate-id-guard b/.duplicate-id-guard index d99e2fc..3b331fd 100644 --- a/.duplicate-id-guard +++ b/.duplicate-id-guard @@ -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 - diff --git a/crates/hyper/RUSTSEC-0000-0000.md b/crates/hyper/RUSTSEC-2021-0078.md similarity index 94% rename from crates/hyper/RUSTSEC-0000-0000.md rename to crates/hyper/RUSTSEC-2021-0078.md index d17227c..3a30352 100644 --- a/crates/hyper/RUSTSEC-0000-0000.md +++ b/crates/hyper/RUSTSEC-2021-0078.md @@ -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.