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.
futures-rustls(3 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-io | ^0.3 | 0.3.31 | up to date |
| rustls-pki-types | ^1 | 1.12.0 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.28 | maybe insecure |
(6 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3.1 | 0.3.31 | up to date |
| lazy_static | ^1 | 1.5.0 | up to date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| smol | ^1 | 2.0.2 | out of date |
| rustls-webpki | ^0.102 | 0.103.3 | out of date |
| webpki-roots | ^0.26 | 1.0.1 | out of date |
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.