Skip to content

chore(deps): update rust crate ring to v0.17.12 [security]#55

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/crate-ring-vulnerability
Open

chore(deps): update rust crate ring to v0.17.12 [security]#55
renovate[bot] wants to merge 1 commit intomainfrom
renovate/crate-ring-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 7, 2025

This PR contains the following updates:

Package Type Update Change
ring dependencies patch 0.17.80.17.12

GitHub Vulnerability Alerts

CVE-2025-4432

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.


Release Notes

briansmith/ring (ring)

v0.17.12

============================
Bug fix: #​2447 for denial of service (DoS).

  • Fixes a panic in ring::aead::quic::HeaderProtectionKey::new_mask() when
    integer 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.

  • Fixes a panic on 64-bit targets in ring::aead::{AES_128_GCM, AES_256_GCM}
    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.


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title fix(deps): update rust crate ring to v0.17.12 [security] fix(deps): update rust crate ring to v0.17.13 [security] May 9, 2025
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch from c9f8fad to 0b9535b Compare May 9, 2025 23:33
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch from 0b9535b to 65218ed Compare August 10, 2025 12:55
@renovate renovate bot changed the title fix(deps): update rust crate ring to v0.17.13 [security] chore(deps): update rust crate ring to v0.17.13 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch from 65218ed to d53949f Compare December 10, 2025 13:44
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch from d53949f to ff45ae8 Compare December 30, 2025 01:42
@renovate renovate bot changed the title chore(deps): update rust crate ring to v0.17.13 [security] chore(deps): update rust crate ring to v0.17.12 [security] Dec 30, 2025
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch from ff45ae8 to 74b9699 Compare February 2, 2026 19:39
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch from 74b9699 to e0d86b6 Compare February 12, 2026 13:57
@renovate renovate bot changed the title chore(deps): update rust crate ring to v0.17.12 [security] chore(deps): update rust crate ring to v0.17.12 [security] - autoclosed Feb 17, 2026
@renovate renovate bot closed this Feb 17, 2026
@renovate renovate bot deleted the renovate/crate-ring-vulnerability branch February 17, 2026 15:05
@renovate renovate bot changed the title chore(deps): update rust crate ring to v0.17.12 [security] - autoclosed chore(deps): update rust crate ring to v0.17.12 [security] Feb 17, 2026
@renovate renovate bot reopened this Feb 17, 2026
@renovate renovate bot force-pushed the renovate/crate-ring-vulnerability branch 2 times, most recently from e0d86b6 to 696a5c5 Compare February 17, 2026 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants