Skip to content

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

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

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/crate-ring-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Mar 7, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
ring dependencies patch 0.17.80.17.12

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

CVE-2025-4432 / GHSA-4p46-pwfr-66x6

More information

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

  • CVSS Score: 6.6 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


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: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR becomes conflicted, 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
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from 696a5c5 to c12704a Compare March 13, 2026 15:53
@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 Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@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] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch 2 times, most recently from c12704a to 2e20c0f Compare March 30, 2026 21:53
@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 Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@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] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch 2 times, most recently from 2e20c0f to eae31ed Compare April 27, 2026 22:50
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from eae31ed to 49b847c Compare May 18, 2026 12:01
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from 49b847c to 9d01487 Compare July 20, 2026 19:50
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from 9d01487 to 8e6f60e Compare August 12, 2026 00:13
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from 8e6f60e to 11e7c4c Compare August 26, 2026 18:42
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from 11e7c4c to 673969b Compare September 7, 2026 18:16
@renovate
renovate Bot force-pushed the renovate/crate-ring-vulnerability branch from 673969b to 93f5591 Compare September 15, 2026 16:12
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