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.

Crate hyper-rustls

Dependencies

(10 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ct-logs^0.80.9.0out of date
 futures-util^0.3.10.3.17up to date
 hyper ⚠️^0.140.14.13maybe insecure
 log^0.4.40.4.14up to date
 rustls^0.190.19.1up to date
 rustls-native-certs^0.5.00.5.0up to date
 tokio ⚠️^1.01.12.0maybe insecure
 tokio-rustls^0.220.22.0up to date
 webpki^0.21.00.22.0out of date
 webpki-roots^0.210.22.0out of date

Dev dependencies

(3 total, 2 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.3.00.3.2up to date
 hyper ⚠️^0.140.14.13maybe insecure
 tokio ⚠️^1.01.12.0maybe insecure

Security Vulnerabilities

tokio: Task dropped in wrong thread when aborting `LocalSet` task

RUSTSEC-2021-0072

When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet.

This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.

See tokio#3929 for more details.

hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling

RUSTSEC-2021-0078

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: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss

RUSTSEC-2021-0079

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.