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-tls

Dependencies

(11 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.300.3.31up to date
 futures-rustls^0.26.00.26.0up to date
 libp2p-core^0.43.10.43.1up to date
 libp2p-identity^0.2.120.2.12up to date
 rcgen^0.130.14.1out of date
 ring^0.17.120.17.14up to date
 rustls ⚠️^0.23.90.23.28maybe insecure
 thiserror^22.0.12up to date
 rustls-webpki^0.1030.103.3up to date
 x509-parser^0.17.00.17.0up to date
 yasna^0.5.20.5.2up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 hex-literal^0.4.11.0.0out of date
 libp2p-core^0.43.10.43.1up to date
 libp2p-identity^0.2.120.2.12up to date
 libp2p-swarm^0.47.00.47.0up to date
 libp2p-yamux^0.47.00.47.0up to date
 tokio^1.381.46.1up 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.