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 rtc-dtls

Dependencies

(28 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aes^0.80.8.4up to date
 aes-gcm^0.100.10.3up to date
 bincode^11.3.3up to date
 byteorder^11.5.0up to date
 bytes^1.41.6.1up to date
 cbc^0.10.1.2up to date
 ccm^0.50.5.0up to date
 der-parser^99.0.0up to date
 hkdf^0.120.12.4up to date
 hmac^0.120.12.1up to date
 log^0.40.4.22up to date
 p256^0.130.13.2up to date
 p384^0.130.13.0up to date
 pem^33.0.4up to date
 rand^0.80.8.5up to date
 rand_core^0.60.6.4up to date
 rcgen^0.120.13.1out of date
 ring^0.170.17.8up to date
 rustls ⚠️^0.210.23.11out of date
 sec1^0.70.7.3up to date
 serde^11.0.204up to date
 sha1^0.100.10.6up to date
 sha2^0.100.10.8up to date
 rtc-shared^0.1.10.2.1out of date
 subtle^22.6.1up to date
 thiserror^11.0.63up to date
 x25519-dalek^22.0.1up to date
 x509-parser^0.160.16.0up to date

Dev dependencies

(8 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^11.0.86up to date
 chrono^0.4.340.4.38up to date
 clap^44.5.9up to date
 core_affinity^0.80.8.1up to date
 ctrlc^33.4.4up to date
 env_logger^0.110.11.3up to date
 futures^0.30.3.30up to date
 local-sync^0.10.1.1up 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.