Deps.rs

webrtc-dtls 0.8.0

[![dependency status](https://deps.rs/crate/webrtc-dtls/0.8.0/status.svg)](https://deps.rs/crate/webrtc-dtls/0.8.0)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate webrtc-dtls

Dependencies

(29 total, 23 outdated, 1 insecure)

CrateRequiredLatestStatus
 aes^0.80.9.3out of date
 aes-gcm^0.100.11.1out of date
 async-trait^0.10.1.92up to date
 bincode^13.0.0out of date
 byteorder^11.5.0up to date
 cbc^0.10.2.1out of date
 ccm^0.50.6.1out of date
 der-parser^8.110.0.0out of date
 hkdf^0.120.13.0out of date
 hmac^0.120.13.0out of date
 log^0.40.4.34up to date
 p256^0.130.14.0out of date
 p384^0.130.14.0out of date
 pem^34.0.0out of date
 rand^0.80.10.3out of date
 rand_core^0.60.10.1out of date
 rcgen^0.110.14.10out of date
 ring ⚠️^0.16.190.17.14insecure
 rustls^0.210.23.45out of date
 sec1^0.70.8.1out of date
 serde^11.0.229up to date
 sha1^0.100.11.0out of date
 sha2^0.100.11.0out of date
 subtle^22.6.1up to date
 thiserror^12.0.21out of date
 tokio^1.32.01.53.1up to date
 webrtc-util^0.80.17.2out of date
 x25519-dalek^23.0.0out of date
 x509-parser^0.150.18.1out of date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 chrono^0.4.280.4.45up to date
 clap^34.6.7out of date
 env_logger^0.100.11.11out of date
 tokio-test^0.40.4.6up 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.