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-quic(17 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| compio-buf | ^0.5.1 | 0.5.1 | up to date |
| compio-io | ^0.6.0 | 0.6.0 | up to date |
| compio-log | ^0.1.0 | 0.1.0 | up to date |
| compio-net | ^0.7.0 | 0.7.0 | up to date |
| compio-runtime | ^0.7.0 | 0.7.0 | up to date |
| flume | ^0.11.0 | 0.11.1 | up to date |
| futures-util | ^0.3.29 | 0.3.31 | up to date |
| h3 | ^0.0.6 | 0.0.8 | out of date |
| libc | ^0.2.164 | 0.2.172 | up to date |
| quinn-proto | ^0.11.9 | 0.11.12 | up to date |
| rustc-hash | ^2.0.0 | 2.1.1 | up to date |
| rustls ⚠️ | ^0.23.1 | 0.23.27 | maybe insecure |
| rustls-native-certs | ^0.8.0 | 0.8.1 | up to date |
| rustls-platform-verifier | ^0.5.0 | 0.5.3 | up to date |
| thiserror | ^2.0.3 | 2.0.12 | up to date |
| webpki-roots | ^0.26.3 | 1.0.0 | out of date |
| windows-sys | ^0.52.0 | 0.59.0 | out of date |
(13 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| compio-dispatcher | ^0.6.0 | 0.6.0 | up to date |
| compio-driver | ^0.7.0 | 0.7.0 | up to date |
| compio-fs | ^0.7.0 | 0.7.0 | up to date |
| compio-macros | ^0.1.2 | 0.1.2 | up to date |
| compio-runtime | ^0.7.0 | 0.7.0 | up to date |
| criterion | ^0.5.1 | 0.6.0 | out of date |
| http | ^1.1.0 | 1.3.1 | up to date |
| quinn | ^0.11.6 | 0.11.8 | up to date |
| rand | ^0.9.0 | 0.9.1 | up to date |
| rcgen | ^0.13.1 | 0.13.2 | up to date |
| socket2 | ^0.5.6 | 0.5.9 | up to date |
| tokio | ^1.33.0 | 1.45.0 | up to date |
| tracing-subscriber | ^0.3.18 | 0.3.19 | 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.