This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
hyper-openssl(3 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| antidote | ^1.0 | 1.0.0 | up to date |
| hyper ⚠️ | ^0.10 | 1.3.1 | out of date |
| openssl ⚠️ | ^0.9.10 | 0.10.64 | 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.
openssl: `openssl` `X509NameBuilder::build` returned object is not thread safeOpenSSL has a modified bit that it can set on on X509_NAME objects. If this
bit is set then the object is not thread-safe even when it appears the code is
not modifying the value.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file readSubjectAlternativeName and ExtendedKeyUsage arguments were parsed using the OpenSSL
function X509V3_EXT_nconf. This function parses all input using an OpenSSL mini-language
which can perform arbitrary file reads.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `X509Extension::new` and `X509Extension::new_nid` null pointer dereferenceThese functions would crash when the context argument was None with certain extension types.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.