Deps.rs

RustCrypto / ring-compat

[![dependency status](https://deps.rs/repo/github/RustCrypto/ring-compat/status.svg)](https://deps.rs/repo/github/RustCrypto/ring-compat)

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 ring-compat

Dependencies

(11 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 generic-array^0.141.2.0out of date
 ring ⚠️^0.170.17.14maybe insecure
 aead^0.50.5.2up to date
 digest^0.100.10.7up to date
 ecdsa^0.160.16.9up to date
 ed25519^2.22.2.3up to date
 p256^0.130.13.2up to date
 p384^0.130.13.1up to date
 pkcs8^0.100.10.2up to date
 rand_core^0.6.40.9.3out of date
 signature^22.2.0up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 hex-literal^0.41.0.0out of date
 digest^0.100.10.7up 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.