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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2025-1225 advisory.

    Issue summary: An application trying to decrypt CMS messages encrypted usingpassword based encryption can     trigger an out-of-bounds read and write.

    Impact summary: This out-of-bounds read may trigger a crash which leads toDenial of Service for an     application. The out-of-bounds write can causea memory corruption which can have various consequences     includinga Denial of Service or Execution of attacker-supplied code.

    Although the consequences of a successful exploit of this vulnerabilitycould be severe, the probability     that the attacker would be able toperform it is low. Besides, password based (PWRI) encryption support in     CMSmessages is very rarely used. For that reason the issue was assessed asModerate severity according to     our Security Policy.

    The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by thisissue, as the CMS     implementation is outside the OpenSSL FIPS moduleboundary. (CVE-2025-9230)

    Issue summary: A timing side-channel which could potentially allow remoterecovery of the private key     exists in the SM2 algorithm implementation on 64 bitARM platforms.

    Impact summary: A timing side-channel in SM2 signature computations on 64 bitARM 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 sothis CVE is not relevant in     most TLS contexts.  However, given that it ispossible to add support for such certificates via a custom     provider, coupledwith the fact that in such a custom provider context the private key may berecoverable     via remote timing measurements, we consider this to be a Moderateseverity issue.

    The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by thisissue, as SM2 is not an     approved algorithm. (CVE-2025-9231)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 41 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-e6f76d56fc advisory.

    Resolves: CVE-2025-9230, CVE-2025-9231, CVE-2025-9232

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 42 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-c355a1291c advisory.

    Resolves: CVE-2025-9230, CVE-2025-9231, CVE-2025-9232

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 00e912c5-9e92-11f0-bc5f-8447094a420f advisory.

    The OpenSSL project reports reports:
    Out-of-bounds read & write in RFC 3211 KEK Unwrap     Timing side-channel in SM2 algorithm on 64-bit ARM     Fix Out-of-bounds read in HTTP client no_proxy handling

Tenable has extracted the preceding description block directly from the FreeBSD security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 12 / 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6015 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6015-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     October 01, 2025                      https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : openssl     CVE ID         : CVE-2025-9230 CVE-2025-9231 CVE-2025-9232

    Multiple vulnerabilities have been discovered in OpenSSL, a Secure     Sockets Layer toolkit, which may result in denial of service or     information leaks.

    Additional details can be found in the upstream advisory:
    https://openssl-library.org/news/secadv/20250930.txt

    For the oldstable distribution (bookworm), these problems have been fixed     in version 3.0.17-1~deb12u3.

    For the stable distribution (trixie), these problems have been fixed in     version 3.5.1-1+deb13u1.

    We recommend that you upgrade your openssl packages.

    For the detailed security status of openssl please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/openssl

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2025-9231)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS / 25.04 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-7786-1 advisory.

    Stanislav Fort discovered that OpenSSL incorrectly handled memory when trying to decrypt CMS messages     encrypted with password-based encryption. An attacker could possibly use this issue to cause a denial of     service or execute arbitrary code. (CVE-2025-9230)

    Stanislav Fort discovered that OpenSSL had a timing side-channel in SM2 signature computations on ARM     platforms. A remote attacker could possibly use this issue to recover private data. This issue only     affected Ubuntu 25.04. (CVE-2025-9231)

    Stanislav Fort discovered that OpenSSL incorrectly handled memory during HTTP requests when no_proxy     environment variable is set. An attacker could possibly use this issue to cause a denial of service. This     issue only affected Ubuntu 25.04. (CVE-2025-9232)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of OpenSSL installed on the remote host is prior to 3.2.6. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.2.6 advisory.

  - 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. (CVE-2025-9231)

  - Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds     read if the 'no_proxy' environment variable is set and the host portion of the authority component of the     HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to     Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by     applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol)     client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be     controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash.
    Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the     OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned     reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch     releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and     3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module     boundary. (CVE-2025-9232)

  - Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can     trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which     leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which     can have various consequences including a Denial of Service or Execution of attacker-supplied code.
    Although the consequences of a successful exploit of this vulnerability could be severe, the probability     that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in     CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to     our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue,     as the CMS implementation is outside the OpenSSL FIPS module boundary. (CVE-2025-9230)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of OpenSSL installed on the remote host is prior to 3.5.4. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.5.4 advisory.

  - 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. (CVE-2025-9231)

  - Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds     read if the 'no_proxy' environment variable is set and the host portion of the authority component of the     HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to     Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by     applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol)     client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be     controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash.
    Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the     OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned     reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch     releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and     3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module     boundary. (CVE-2025-9232)

  - Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can     trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which     leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which     can have various consequences including a Denial of Service or Execution of attacker-supplied code.
    Although the consequences of a successful exploit of this vulnerability could be severe, the probability     that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in     CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to     our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue,     as the CMS implementation is outside the OpenSSL FIPS module boundary. (CVE-2025-9230)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of OpenSSL installed on the remote host is prior to 3.4.3. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.4.3 advisory.

  - 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. (CVE-2025-9231)

  - Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds     read if the 'no_proxy' environment variable is set and the host portion of the authority component of the     HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to     Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by     applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol)     client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be     controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash.
    Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the     OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned     reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch     releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and     3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module     boundary. (CVE-2025-9232)

  - Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can     trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which     leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which     can have various consequences including a Denial of Service or Execution of attacker-supplied code.
    Although the consequences of a successful exploit of this vulnerability could be severe, the probability     that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in     CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to     our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue,     as the CMS implementation is outside the OpenSSL FIPS module boundary. (CVE-2025-9230)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of OpenSSL installed on the remote host is prior to 3.3.5. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.3.5 advisory.

  - 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. (CVE-2025-9231)

  - Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds     read if the 'no_proxy' environment variable is set and the host portion of the authority component of the     HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to     Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by     applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol)     client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be     controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash.
    Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the     OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned     reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch     releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and     3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module     boundary. (CVE-2025-9232)

  - Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can     trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which     leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which     can have various consequences including a Denial of Service or Execution of attacker-supplied code.
    Although the consequences of a successful exploit of this vulnerability could be severe, the probability     that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in     CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to     our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue,     as the CMS implementation is outside the OpenSSL FIPS module boundary. (CVE-2025-9230)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
270526	Amazon Linux 2023 : openssl, openssl-devel, openssl-fips-provider-latest (ALAS2023-2025-1225)	Nessus	Amazon Linux Local Security Checks	medium
270121	Fedora 41 : openssl (2025-e6f76d56fc)	Nessus	Fedora Local Security Checks	medium
269689	Fedora 42 : openssl (2025-c355a1291c)	Nessus	Fedora Local Security Checks	medium
266387	FreeBSD : OpenSSL -- multiple vulnerabilities (00e912c5-9e92-11f0-bc5f-8447094a420f)	Nessus	FreeBSD Local Security Checks	medium
266357	Debian dsa-6015 : libcrypto3-udeb - security update	Nessus	Debian Local Security Checks	medium
266348	Linux Distros Unpatched Vulnerability : CVE-2025-9231	Nessus	Misc.	medium
266334	Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS / 25.04 : OpenSSL vulnerabilities (USN-7786-1)	Nessus	Ubuntu Local Security Checks	medium
266319	OpenSSL 3.2.0 < 3.2.6 Multiple Vulnerabilities	Nessus	Web Servers	medium
266298	OpenSSL 3.5.0 < 3.5.4 Multiple Vulnerabilities	Nessus	Web Servers	medium
266295	OpenSSL 3.4.0 < 3.4.3 Multiple Vulnerabilities	Nessus	Web Servers	medium
266293	OpenSSL 3.3.0 < 3.3.5 Multiple Vulnerabilities	Nessus	Web Servers	medium

Detections

Analytics

CVE-2025-9231

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium