CVE-2025-9231
Timing side-channel in SM2 algorithm on 64 bit ARM
No known exploitation. EPSS puts it in the 76th percentile. Fixed versions are out.
No public exploit knownFix5 products8 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.119301
What to do
Find your product and version, then upgrade to the build on the right.
- OpenSSLAffected: ≥ 3.5.0, < 3.5.4Upgrade to: 3.5.4Affected: ≥ 3.4.0, < 3.4.3Upgrade to: 3.4.3Affected: ≥ 3.3.0, < 3.3.5Upgrade to: 3.3.5Affected: ≥ 3.2.0, < 3.2.6Upgrade to: 3.2.6Stated by: CVE record
- Siemens Ruggedcom Rst2428p FirmwareAffected: < 4.0Upgrade to: 4.0Stated by: NVD
- Siemens Sidis Secured Smartplug FirmwareAffected: < 7.26.0310Upgrade to: 7.26.0310Stated by: NVD
- Siemens Sinec OsAffected: < 3.3Upgrade to: 3.3Stated by: NVD
- Siemens Simatic Cn 4100 FirmwareAffected: < 5.0Upgrade to: 5.0Stated by: NVD
Versions as the sources state them. 2 more products have version data. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
1.6% chance of exploitation activity in the next 30 days, which ranks it in the 76th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
13 events over 405 days, from the signal feeds we watch.
- Patch availablerecord updated
- Patch availablepatch available, record updated, record updated
- Patch availablerecord updated
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Scored 5.9 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Siemens, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI