hyper is an HTTP library for rust. hypers HTTP/1 server code had a flaw that incorrectly parses and accepts requests with a Content-Length header with a prefixed plus sign, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that doesnt parse such Content-Length headers, but forwards them, can result in request smuggling or desync attacks. The flaw exists in all prior versions of hyper prior to 0.14.10, if built with rustc v1.5.0 or newer. The vulnerability is patched in hyper version 0.14.10. Two workarounds exist: One may reject requests manually that contain a plus sign prefix in the Content-Length header or ensure any upstream proxy handles Content-Length headers with a plus sign prefix.
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Hyper | Hyper | * | 0.14.10 (excluding) |
| Rust-hyper | Ubuntu | esm-apps/focal | * |
| Rust-hyper | Ubuntu | focal | * |
| Rust-hyper | Ubuntu | hirsute | * |
| Rust-hyper | Ubuntu | impish | * |
| Rust-hyper | Ubuntu | kinetic | * |
| Rust-hyper | Ubuntu | trusty | * |
| Rust-hyper | Ubuntu | upstream | * |
| Rust-hyper | Ubuntu | xenial | * |
HTTP requests or responses (“messages”) can be malformed or unexpected in ways that cause web servers or clients to interpret the messages in different ways than intermediary HTTP agents such as load balancers, reverse proxies, web caching proxies, application firewalls, etc. For example, an adversary may be able to add duplicate or different header fields that a client or server might interpret as one set of messages, whereas the intermediary might interpret the same sequence of bytes as a different set of messages. For example, discrepancies can arise in how to handle duplicate headers like two Transfer-encoding (TE) or two Content-length (CL), or the malicious HTTP message will have different headers for TE and CL. The inconsistent parsing and interpretation of messages can allow the adversary to “smuggle” a message to the client/server without the intermediary being aware of it. This weakness is usually the result of the usage of outdated or incompatible HTTP protocol versions in the HTTP agents.