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.
compio-tls(6 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| compio-buf | ^0.7.1 | 0.8.1 | out of date |
| compio-io | ^0.8.4 | 0.9.1 | out of date |
| futures-rustls | ^0.26.0 | 0.26.0 | up to date |
| futures-util | ^0.3.29 | 0.3.32 | up to date |
| native-tls | ^0.2.13 | 0.2.18 | up to date |
| rustls ⚠️ | ^0.23.1 | 0.23.40 | maybe insecure |
(6 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| compio-macros | ^0.1.2 | 0.1.2 | up to date |
| compio-net | ^0.10.0 | 0.11.1 | out of date |
| compio-runtime | ^0.10.0 | 0.11.0 | out of date |
| futures-rustls | ^0.26.0 | 0.26.0 | up to date |
| rustls ⚠️ | ^0.23.1 | 0.23.40 | maybe insecure |
| rustls-native-certs | ^0.8.0 | 0.8.3 | up to 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.