Deps.rs

webrtc-rs / rmls

[![dependency status](https://deps.rs/repo/github/webrtc-rs/rmls/status.svg)](https://deps.rs/repo/github/webrtc-rs/rmls)

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 rmls

Dependencies

(21 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 thiserror^12.0.12out of date
 bytes^11.10.1up to date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 hpke^0.10.00.13.0out of date
 getrandom^0.2.100.3.1out of date
 rand_core^0.6.40.9.3out of date
 rand_chacha^0.3.10.9.0out of date
 ring ⚠️^0.16.200.17.14out of date
 sha2^0.10.70.10.8up to date
 hmac^0.12.10.12.1up to date
 hkdf^0.12.30.12.4up to date
 ed25519-dalek^2.0.02.1.1up to date
 ecdsa^0.16.80.16.9up to date
 sec1^0.7.30.7.3up to date
 signature^2.1.02.2.0up to date
 aead^0.5.20.5.2up to date
 aes-gcm^0.10.20.10.3up to date
 chacha20poly1305^0.10.10.10.1up to date
 p256^0.13.20.13.2up to date
 p384^0.13.00.13.1up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 hex^0.40.4.3up 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.