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

Dependencies

(14 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.300.3.31up to date
 futures-timer^3.0.33.0.3up to date
 if-watch^3.2.13.2.1up to date
 libp2p-core^0.43.10.43.1up to date
 libp2p-identity^0.2.120.2.12up to date
 libp2p-tls^0.6.20.6.2up to date
 quinn^0.11.60.11.8up to date
 rand^0.8.50.9.1out of date
 ring^0.17.120.17.14up to date
 rustls ⚠️^0.23.90.23.29maybe insecure
 socket2^0.5.70.6.0out of date
 thiserror^22.0.12up to date
 tokio^1.381.46.1up to date
 tracing^0.1.410.1.41up to date

Dev dependencies

(7 total, all up-to-date)

CrateRequiredLatestStatus
 libp2p-identity^0.2.120.2.12up to date
 libp2p-noise^0.46.10.46.1up to date
 libp2p-tcp^0.44.00.44.0up to date
 libp2p-yamux^0.47.00.47.0up to date
 quickcheck^11.0.3up to date
 tokio^1.381.46.1up to date
 tracing-subscriber^0.3.190.3.19up 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.