Security update for openssl-3 SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2025:20164-1 Final 1 1 2025-12-15T18:16:15Z current 2025-12-15T18:16:15Z 2025-12-15T18:16:15Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for openssl-3 This update for openssl-3 fixes the following issues: - CVE-2025-9230: Fixed out-of-bounds read & write in RFC 3211 KEK unwrap (bsc#1250232) - CVE-2025-9231: Fixedk timing side-channel in SM2 algorithm on 64 bit ARM (bsc#1250233) - CVE-2025-9232: Fixed out-of-bounds read in HTTP client no_proxy handling (bsc#1250234) The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). openSUSE-Leap-16.0-107 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1250232 SUSE Bug 1250232 https://bugzilla.suse.com/1250233 SUSE Bug 1250233 https://bugzilla.suse.com/1250234 SUSE Bug 1250234 https://www.suse.com/security/cve/CVE-2025-9230/ SUSE CVE CVE-2025-9230 page https://www.suse.com/security/cve/CVE-2025-9231/ SUSE CVE CVE-2025-9231 page https://www.suse.com/security/cve/CVE-2025-9232/ SUSE CVE CVE-2025-9232 page openSUSE Leap 16.0 libopenssl-3-devel-3.5.0-160000.4.1 libopenssl-3-fips-provider-3.5.0-160000.4.1 libopenssl-3-fips-provider-x86-64-v3-3.5.0-160000.4.1 libopenssl3-3.5.0-160000.4.1 libopenssl3-x86-64-v3-3.5.0-160000.4.1 openssl-3-3.5.0-160000.4.1 openssl-3-doc-3.5.0-160000.4.1 libopenssl-3-devel-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 libopenssl-3-fips-provider-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 libopenssl-3-fips-provider-x86-64-v3-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 libopenssl3-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 libopenssl3-x86-64-v3-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 openssl-3-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 openssl-3-doc-3.5.0-160000.4.1 as a component of openSUSE Leap 16.0 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 openSUSE Leap 16.0:libopenssl-3-devel-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl-3-fips-provider-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl-3-fips-provider-x86-64-v3-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl3-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl3-x86-64-v3-3.5.0-160000.4.1 openSUSE Leap 16.0:openssl-3-3.5.0-160000.4.1 openSUSE Leap 16.0:openssl-3-doc-3.5.0-160000.4.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2025-9230.html CVE-2025-9230 https://bugzilla.suse.com/1250232 SUSE Bug 1250232 https://bugzilla.suse.com/1250410 SUSE Bug 1250410 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 openSUSE Leap 16.0:libopenssl-3-devel-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl-3-fips-provider-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl-3-fips-provider-x86-64-v3-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl3-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl3-x86-64-v3-3.5.0-160000.4.1 openSUSE Leap 16.0:openssl-3-3.5.0-160000.4.1 openSUSE Leap 16.0:openssl-3-doc-3.5.0-160000.4.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2025-9231.html CVE-2025-9231 https://bugzilla.suse.com/1250233 SUSE Bug 1250233 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 openSUSE Leap 16.0:libopenssl-3-devel-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl-3-fips-provider-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl-3-fips-provider-x86-64-v3-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl3-3.5.0-160000.4.1 openSUSE Leap 16.0:libopenssl3-x86-64-v3-3.5.0-160000.4.1 openSUSE Leap 16.0:openssl-3-3.5.0-160000.4.1 openSUSE Leap 16.0:openssl-3-doc-3.5.0-160000.4.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2025-9232.html CVE-2025-9232 https://bugzilla.suse.com/1250234 SUSE Bug 1250234