HistoryEdit

RUSTSEC-2021-0078

Lenient hyper header parsing of Content-Length could allow request smuggling

Issued
Package
hyper (crates.io)
Type
Vulnerability
Keywords
#parsing #http
Aliases
Details
https://github.com/hyperium/hyper/security/advisories/GHSA-f3pg-qwvg-p99c
CVSS Score
5.3 MEDIUM
CVSS Details
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Patched
  • >=0.14.10
Keywords
#parsing #http

Description

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 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 vulnerability is unlikely.