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 compio-quic

Dependencies

(18 total, 1 possibly insecure)

CrateRequiredLatestStatus
 compio-buf^0.7.00.7.0up to date
 compio-io^0.8.00.8.2up to date
 compio-log^0.1.00.1.0up to date
 compio-net^0.9.00.9.0up to date
 compio-runtime^0.9.00.9.3up to date
 flume^0.11.00.11.1up to date
 futures-util^0.3.290.3.31up to date
 h3^0.0.80.0.8up to date
 h3-datagram^0.0.20.0.2up to date
 libc^0.2.1640.2.177up to date
 quinn-proto^0.11.100.11.13up to date
 rustc-hash^2.0.02.1.1up to date
 rustls ⚠️^0.23.10.23.35maybe insecure
 rustls-native-certs^0.8.00.8.2up to date
 rustls-platform-verifier^0.6.00.6.2up to date
 thiserror^2.0.32.0.17up to date
 webpki-roots^1.0.01.0.4up to date
 windows-sys^0.61.00.61.2up to date

Dev dependencies

(13 total, all up-to-date)

CrateRequiredLatestStatus
 compio-dispatcher^0.8.00.8.1up to date
 compio-driver^0.9.00.9.1up to date
 compio-fs^0.9.00.9.0up to date
 compio-macros^0.1.20.1.2up to date
 compio-runtime^0.9.00.9.3up to date
 criterion^0.7.00.7.0up to date
 http^1.1.01.3.1up to date
 quinn^0.11.60.11.9up to date
 rand^0.9.00.9.2up to date
 rcgen^0.14.10.14.5up to date
 socket2^0.6.00.6.1up to date
 tokio^1.33.01.48.0up to date
 tracing-subscriber^0.3.180.3.20up to date

Security Vulnerabilities

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

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.