Deps.rs

stun 0.5.0

[![dependency status](https://deps.rs/crate/stun/0.5.0/status.svg)](https://deps.rs/crate/stun/0.5.0)

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 stun

Dependencies

(11 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.210.22.1out of date
 crc^33.3.0up to date
 lazy_static^11.5.0up to date
 md-5^0.100.10.6up to date
 rand^0.80.9.1out of date
 ring ⚠️^0.160.17.14out of date
 subtle^2.42.6.1up to date
 thiserror^12.0.12out of date
 tokio^1.32.01.45.0up to date
 url^22.5.4up to date
 webrtc-util^0.80.10.0out of date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 clap^34.5.37out of date
 criterion^0.50.5.1up to date
 tokio-test^0.40.4.4up 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.