This project contains known security vulnerabilities. Find detailed information at the bottom.
hyper-openssl(10 total, 4 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| antidote | ^1.0.0 | 1.0.0 | up to date |
| bytes | ^0.4 | 1.12.1 | out of date |
| futures | ^0.1.14 | 0.3.34 | out of date |
| hyper ⚠️ | ^0.12.14 | 1.11.1 | insecure |
| lazy_static | ^1.0 | 1.5.0 | up to date |
| linked_hash_set | ^0.1 | 0.1.6 | up to date |
| openssl | ^0.10.19 | 0.10.81 | up to date |
| openssl-sys | ^0.9.26 | 0.9.117 | up to date |
| tokio-io | ^0.1.2 | 0.1.13 | up to date |
| tokio-openssl | ^0.3 | 0.6.5 | out of date |
(2 total, 2 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| hyper ⚠️ | ^0.12 | 1.11.1 | insecure |
| tokio | ^0.1 | 1.53.1 | out of date |
hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smugglinghyper'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: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data lossWhen 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.