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, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.290.3.30up to date
 futures-rustls^0.24.00.26.0out of date
 libp2p-core^0.41.00.41.2up to date
 libp2p-identity^0.2.70.2.8up to date
 rcgen^0.11.30.13.1out of date
 ring^0.16.200.17.8out of date
 rustls ⚠️^0.21.80.23.5out of date
 thiserror^1.0.501.0.60up to date
 rustls-webpki^0.101.40.102.3out of date
 x509-parser^0.15.10.16.0out of date
 yasna^0.5.20.5.2up to date

Dev dependencies

(7 total, all up-to-date)

CrateRequiredLatestStatus
 hex^0.4.30.4.3up to date
 hex-literal^0.4.10.4.1up to date
 libp2p-core^0.41.00.41.2up to date
 libp2p-identity^0.2.70.2.8up to date
 libp2p-swarm^0.44.00.44.2up to date
 libp2p-yamux^0.45.00.45.1up to date
 tokio^1.33.01.37.0up to date

Security Vulnerabilities

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.