CVE-2025-9231 Affecting openssl-engine-capi package, versions <3.5.4-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-OPENSSLENGINECAPI-13319583
  • published6 Oct 2025
  • disclosed30 Sept 2025

Introduced: 30 Sep 2025

NewCVE-2025-9231  (opens in a new tab)

How to fix?

Upgrade Minimos:latest openssl-engine-capi to version 3.5.4-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl-engine-capi package and not the openssl-engine-capi package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1