RUSTSEC-2025-0009

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2025-0009

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2025-0009.json

JSON Data

https://api.osv.dev/v1/vulns/RUSTSEC-2025-0009

Published

2025-03-06T12:00:00Z

Modified

2025-03-06T21:44:11Z

Summary

Some AES functions may panic when overflow checking is enabled.

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.

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / ring

Package

Name: ring; View open source insights on deps.dev
Purl: pkg:cargo/ring

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Fixed

0.17.12

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific

{
    "cvss": null,
    "informational": null,
    "categories": [
        "denial-of-service"
    ]
}