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 turn

Dependencies

(12 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.89up to date
 base64^0.210.22.1out of date
 futures^0.30.3.32up to date
 log^0.40.4.29up to date
 md-5^0.100.10.6up to date
 rand^0.80.10.0out of date
 ring ⚠️^0.170.17.14maybe insecure
 stun^0.5.10.17.1out of date
 thiserror^12.0.18out of date
 tokio^1.32.01.50.0up to date
 tokio-util^0.70.7.18up to date
 webrtc-util^0.8.10.17.1out of date

Dev dependencies

(6 total, 3 outdated)

CrateRequiredLatestStatus
 chrono^0.4.280.4.44up to date
 clap^34.5.60out of date
 criterion^0.50.8.2out of date
 env_logger^0.100.11.9out of date
 hex^0.40.4.3up to date
 tokio-test^0.40.4.5up to date

Security Vulnerabilities

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.