Deps.rs

webrtc 0.9.0

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

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

Crate webrtc

Dependencies

(36 total, 22 outdated, 1 insecure)

CrateRequiredLatestStatus
 arc-swap^11.9.2up to date
 async-trait^0.10.1.92up to date
 bytes^11.12.1up to date
 cfg-if^11.0.5up to date
 webrtc-data^0.80.17.2out of date
 webrtc-dtls^0.80.12.0out of date
 hex^0.40.4.3up to date
 webrtc-ice^0.100.17.2out of date
 interceptor^0.100.17.2out of date
 lazy_static^1.41.5.0up to date
 log^0.40.4.34up to date
 webrtc-mdns^0.60.17.2out of date
 webrtc-media^0.70.17.2out of date
 pem^34.0.0out of date
 rand^0.80.10.2out of date
 rcgen^0.110.14.10out of date
 regex^1.9.51.13.1up to date
 ring ⚠️^0.160.17.14insecure
 rtcp^0.100.17.2out of date
 rtp^0.90.17.2out of date
 rustls^0.210.23.45out of date
 webrtc-sctp^0.90.17.2out of date
 sdp^0.60.17.2out of date
 serde^11.0.229up to date
 serde_json^11.0.151up to date
 sha2^0.100.11.0out of date
 smol_str^0.20.3.6out of date
 webrtc-srtp^0.110.17.2out of date
 stun^0.50.17.2out of date
 thiserror^12.0.20out of date
 time^0.30.3.55up to date
 tokio^1.32.01.53.1up to date
 turn^0.70.17.2out of date
 url^22.5.8up to date
 webrtc-util^0.80.17.2out of date
 waitgroup^0.10.1.2up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.100.11.11out of 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.