Most recent entries from all

bdu:2022-02054

EUVD-2026-28056

fkie_cve-2021-32714

hyper is an HTTP library for Rust. In versions prior to 0.14.10, hyper's HTTP server and client code had a flaw that could trigger an integer overflow when decoding chunk sizes that are too big. This allows possible data loss, or if combined with an upstream HTTP proxy that allows chunk sizes larger than hyper does, can result in "request smuggling" or "desync attacks." The vulnerability is patched in version 0.14.10. Two possible workarounds exist. One may reject requests manually that contain a `Transfer-Encoding` header or ensure any upstream proxy rejects `Transfer-Encoding` chunk sizes greater than what fits in 64-bit unsigned integers.

GHSA-5h46-h7hh-c6x9 — Integer Overflow in Chunked Transfer-Encoding

Affected: crates.io: hyper

### Summary

hyper's HTTP server and client code had a flaw that could trigger an integer overflow when decoding chunk sizes that are too big. This allows possible data loss, or if combined with an upstream HTTP proxy that allows chunk sizes larger than hyper does, can result in "request smuggling" or "desync attacks".

### Vulnerability

Example:

``` GET / HTTP/1.1 Host: example.com Transfer-Encoding: chunked

f0000000000000003 abc 0

```

hyper only reads the rightmost 64-bit integer as the chunk size. So it reads `f0000000000000003` as `3`. A loss of data can occur since hyper would then read only 3 bytes of the body. Additionally, an HTTP request smuggling vulnerability would occur if using a proxy which instead has prefix truncation in the chunk size, or that understands larger than 64-bit chunk sizes.

Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn

### Impact

To determine if vulnerable to _data loss_, these things must be true:

- **Using HTTP/1.1.** Since HTTP/2 does not use chunked encoding, it is not vulnerable. - **Using hyper as a server or client.** The body would be improperly truncated in either case. - **Users send requests or responses with chunk sizes greater than 18 exabytes**.

To determine if vulnerable to _desync attacks_, these things must be true:

- **Using an upstream proxy that allows chunks sizes larger than 64-bit.** If the proxy rejects chunk sizes that are too large, that request…

gsd-2021-32714

msrc_CVE-2021-32714 — Integer Overflow in Chunked Transfer-Encoding

msrc_CVE-2021-32714

openSUSE-SU-2024:11751-1 — afterburn-5.0.0-6.1 on GA media

afterburn-5.0.0-6.1 on GA media

RUSTSEC-2021-0079 — Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss

Affected: crates.io: hyper

When decoding chunk sizes that are too large, `hyper`'s code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.

To be vulnerable, you must be using `hyper` for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.

UBUNTU-CVE-2021-32714

Affected: Ubuntu:20.04:LTS: rust-hyper