chore(deps): update rust crate ring to 0.17.0 [security]

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ring	dependencies	minor	0.16.9 -> 0.17.0

GitHub Vulnerability Alerts

GHSA-4p46-pwfr-66x6

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.

CVE-2025-4432

A flaw was found in Rust's Ring package. A panic may be triggered when overflow checking is enabled. In the QUIC protocol, this flaw allows an attacker to induce this panic by sending a specially crafted packet. It will likely occur unintentionally in 1 out of every 2**32 packets sent or received.

---

Release Notes

briansmith/ring (ring)

v0.17.13

============================
Increased MSRV to 1.66.0 to avoid bugs in earlier versions so that we can
safely use core::arch::x86_64::__cpuid and core::arch::x86::__cpuid from
Rust in future releases.

AVX2-based VAES-CLMUL implementation. This will be a notable performance
improvement for most newish x86-64 systems. This will likely raise the minimum
binutils version supported for very old Linux distros.

v0.17.12

============================
Bug fix:https://github.com/briansmith/ring/pull/24477 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.

v0.17.1

============================
Support for aarch64-*-linux-uclibc targets was removed, as there do not seem to
be any such targets.

---

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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path keypair/Cargo.toml --package ring@0.16.20 --precise 0.17.12
warning: `/tmp/renovate/repos/github/fluencelabs/trust-graph/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for the requirement `ring = "^0.16.9"`
candidate versions found which didn't match: 0.17.12
location searched: crates.io index
required by package `libp2p-identity v0.2.1`
    ... which satisfies dependency `libp2p-identity = "^0.2.1"` (locked to 0.2.1) of package `fluence-keypair v0.10.4 (/tmp/renovate/repos/github/fluencelabs/trust-graph/keypair)`
    ... which satisfies path dependency `fluence-keypair` (locked to 0.10.4) of package `trust-graph v0.4.11 (/tmp/renovate/repos/github/fluencelabs/trust-graph/trust-graph)`