CVE-2025-4432 json
Ring: some aes functions may panic when overflow checking is enabled in ring
published 2025-03-06 20 mo ago modified 2026-11-05 3 d ago also GHSA-4p46-pwfr-66x6 , GHSA-c86p-w88r-qvqr , GO-2025-3678 , RUSTSEC-2025-0009 , EUVD-2025-14177
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io ring 0.17.12
- rust-ring Debian 14, Debian 13 0.17.14-1
debian advisories DEBIAN-CVE-2025-4432
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250515T200012-1.1
opensuse advisories openSUSE-SU-2025:15135-1
- github.com/briansmith/ring@ec2d3cf commit
- github.com/briansmith/ring#2447 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-4432 updated cvss 5.3
ring: Some AES functions may panic when overflow checking is enabled in ring
-
Red Hat Enterprise Linux 6 firefox, thunderbird Red Hat Enterprise Linux 7 firefox, thunderbird Red Hat Enterprise Linux 8 firefox, thunderbird Red Hat Enterprise Linux 9 gjs, rust, cargo, clippy, polkit, firefox, +18 more Red Hat Enterprise Linux 10 gjs, rust, firefox, snpguest, rpm-ostree, thunderbird, +1 more Red Hat OpenShift Container Platform 4 kata-containersaffected: no fix available “Fix deferred”
+3 more productsfewer
Red Hat Satellite 6 python-maturin, python3.12-maturin Red Hat Trusted Artifact Signer rhtas/tuffer-rhel9, rhtas/tuftool-rhel9 Red Hat Trusted Profile Analyzer rhtpa/rhtpa-trustification-service-rhel9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ring | <0.17.12 >=0.0.0-0, <0.17.12 |
0.17.12 |
| go | github.com/briansmith/ring | all versions |
no fix listed |
Affected products
- Red Hat Red Hat Enterprise Linux 10
- Red Hat Red Hat Enterprise Linux 6
- Red Hat Red Hat Enterprise Linux 7
- Red Hat Red Hat Enterprise Linux 8
- Red Hat Red Hat Enterprise Linux 9
- Red Hat Red Hat OpenShift Container Platform 4
- Red Hat Red Hat Satellite 6
- Red Hat Red Hat Trusted Artifact Signer
- Red Hat Red Hat Trusted Profile Analyzer
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/briansmith/ring/commit/ec2d3cf1d91f148c84e4806b4f0b3c98f6df3b38
web, patch
-
github.com
/briansmith/ring/pull/2447
web, patch
-
access.redhat.com
/security/cve/CVE-2025-4432
vdb-entry, web
-
bugzilla.redhat.com
/show_bug.cgi?id=2350655
issue-tracking, web, report
- github.com /advisories/GHSA-4p46-pwfr-66x6
-
github.com
/briansmith/ring
package, web
-
github.com
/briansmith/ring/blob/main/RELEASES.md#version-01712-2025-03-05
web
-
rustsec.org
/advisories/RUSTSEC-2025-0009.html
web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-4432
advisory
-
crates.io
/crates/ring
package
Sources
- CVE List CVE-2025-4432
- GitHub Advisory GHSA-4p46-pwfr-66x6
- GitHub Advisory GHSA-c86p-w88r-qvqr
- NVD CVE-2025-4432
- OSV GO-2025-3678
- OSV RUSTSEC-2025-0009
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.