CVE-2025-9231
Last modified
CVE-2025-9231 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.. EPSS estimates a 2.23% chance of exploitation in the next 30 days.
Description
Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-9231?
How severe is CVE-2025-9231?
How do I fix CVE-2025-9231?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-9225Stored cross-site scripting (XSS) in the web interface of Mi…5.5
- CVE-2025-9226Zohocorp ManageEngine OpManager, NetFlow Analyzer, and OpUti…4.6
- CVE-2025-9227Zohocorp ManageEngine OpManager versions 128609 and below ar…6.5
- CVE-2025-9228MiR software versions prior to version 3.0.0 have insufficie…4.3
- CVE-2025-9229Information disclosure vulnerability in error handling in Mi…5.3
- CVE-2025-9230Issue summary: An application trying to decrypt CMS messages…7.5
- CVE-2025-9232Issue summary: An application using the OpenSSL HTTP client …5.9
- CVE-2025-9233A security vulnerability has been detected in Scada-LTS up t…5.4
- CVE-2025-9234A vulnerability was detected in Scada-LTS up to 2.7.8.1. The…5.4
- CVE-2025-9235A flaw has been found in Scada-LTS up to 2.7.8.1. The impact…5.4
- CVE-2025-9236A vulnerability has been found in Portabilis i-Educar up to …8.8
- CVE-2025-9237A vulnerability was found in CodeAstro Ecommerce Website 1.0…5.4
Are you affected by CVE-2025-9231?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
