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.
hyper
0.10.16
>=0.14.10
hyper
's HTTP header parser accepted, according to RFC 7230, illegal contents insideContent-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.See advisory page for additional details.