CVE-2025-9231
BaseFortify
Publication date: 2025-09-30
Last updated on: 2025-11-04
Assigner: OpenSSL Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openssl | openssl | 3.5.4 |
| openssl | openssl | 3.0.18 |
| openssl | openssl | 3.2.6 |
| openssl | openssl | 3.3.5 |
| openssl | openssl | 1.1.1zd |
| openssl | openssl | 3.4.3 |
| openssl | openssl | 1.0.2zm |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-385 | Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a timing side-channel issue in the SM2 algorithm implementation on 64-bit ARM platforms. It arises because the modular inversion operation in SM2 cryptographic computations was not performed in constant time, allowing attackers to potentially measure timing differences and recover the private key remotely. The vulnerability specifically affects SM2 signature computations and could leak sensitive key information through timing analysis. [1, 2, 3, 4]
How can this vulnerability impact me? :
If you use SM2 cryptographic keys on 64-bit ARM platforms, an attacker could exploit timing differences during signature computations to recover your private key remotely. This would compromise the security of your cryptographic operations, potentially allowing unauthorized access or impersonation. However, since OpenSSL does not directly support SM2 keys in TLS by default, the risk is limited to environments where custom providers add such support. [1, 2, 3, 4]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your OpenSSL implementation to a version that includes the fix for CVE-2025-9231. The fix involves implementing a constant-time modular inversion algorithm in the SM2 cryptographic operations, which prevents timing side-channel attacks. Applying the relevant patches or upgrading to a version of OpenSSL that contains these commits will address the issue. [1, 2, 3, 4]