Advisory

GHSA-4p46-pwfr-66x6

Also known as: CVE-2025-4432, GHSA-c86p-w88r-qvqr, GO-2025-3678, RUSTSEC-2025-0009

Summary

Some AES functions may panic when overflow checking is enabled in ring

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-03-07 16:23 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

ring

crates.io · All systems

Affected

  • introduced 0, fixed 0.17.12 (semver)

Fixed versions

0.17.12

Fix

  • Fixed version 0.17.12
    cargo update -p ring --precise 0.17.12

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences