Direct naar de inhoud
⚡ Kritieke cyberalerts voor jouw sector & systemen — direct in je inbox. Aanmelden →
cybernieuws.nl Cybersecurity en informatiebeveiling nieuws alerts live · 12 min 122 bronnen 1 kritiek 6 vandaag
CVE's Videos Dagbriefing

← Terug naar CVE-database

CVE-2025-9231

MEDIUM · 5.9 CVSS Gepubliceerd: CWE-385

Beschrijving NL

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.

Origineel (Engels) tonen

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.

Vendors

Siemens Openssl

Affected products

Ruggedcom Rst2428p Firmware Ruggedcom Rst2428p Openssl Sidis Secured Smartplug Firmware Sidis Secured Smartplug Sinec Os Scalance Xc316-8 Scalance Xc319-4 Scalance Xc324-4 Scalance Xc324-4eec Scalance Xc332 Scalance Xc416-8 Scalance Xc419-4 Scalance Xc424-4 Scalance Xc432 Scalance Xch328 Scalance Xcm324 Scalance Xcm328 Scalance Xcm332 Scalance Xr302-32 Scalance Xr322-12 Scalance Xr326-8 Scalance Xr326-8eec Scalance Xr502-32 Scalance Xr522-12 Scalance Xr524-8c Scalance Xr524-8wg Scalance Xr526-8 Scalance Xr526-8c Scalance Xr528-6m Scalance Xr552-12m Scalance Xrh334 Scalance Xrm334 Simatic Cn 4100 Firmware Simatic Cn 4100

References