Security update for openssl-3, libpulp, ulp-macros SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:20014-1 Final 1 1 2025-02-03T08:48:16Z current 2025-02-03T08:48:16Z 2025-02-03T08:48:16Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for openssl-3, libpulp, ulp-macros This update for openssl-3, libpulp, ulp-macros fixes the following issues: openssl-3: - CVE-2024-6119: possible denial of service in X.509 name checks (bsc#1229465) - CVE-2024-5535: SSL_select_next_proto buffer overread (bsc#1227138) - CVE-2024-4741: Fixed a use-after-free with SSL_free_buffers (bsc#1225551) - CVE-2024-4603: Check DSA parameters for excessive sizes before validating (bsc#1224388) - CVE-2024-2511: Fix unconstrained session cache growth in TLSv1.3 (bsc#1222548) - FIPS: Deny SHA-1 signature verification in FIPS provider (bsc#1221365) - FIPS: RSA keygen PCT requirements. (bsc#1221760, bsc#1221753) - FIPS: Check that the fips provider is available before setting it as the default provider in FIPS mode. (bsc#1220523) - FIPS: Port openssl to use jitterentropy (bsc#1220523) - FIPS: Block non-Approved Elliptic Curves (bsc#1221786) - FIPS: Service Level Indicator (bsc#1221365) - FIPS: Output the FIPS-validation name and module version which uniquely identify the FIPS validated module. (bsc#1221751) - FIPS: Add required selftests (bsc#1221760) - FIPS: DH: Disable FIPS 186-4 Domain Parameters (bsc#1221821) - FIPS: Recommendation for Password-Based Key Derivation (bsc#1221827) - FIPS: Zeroization is required (bsc#1221752) - FIPS: Reseed DRBG (bsc#1220690, bsc#1220693, bsc#1220696) - FIPS: NIST SP 800-56Brev2 (bsc#1221824) - FIPS: Approved Modulus Sizes for RSA Digital Signature for FIPS 186-4 (bsc#1221787) - FIPS: Port openssl to use jitterentropy (bsc#1220523) - FIPS: NIST SP 800-56Arev3 (bsc#1221822) - FIPS: Error state has to be enforced (bsc#1221753) - Build with enabled sm2 and sm4 support (bsc#1222899) - fix non-reproducible build issue - Fix HDKF key derivation (bsc#1225291) - Enable livepatching support (bsc#1223428) libpulp: - Update package with libpulp-0.3.5 * Change .so load policy from lazy to eager. * Fix patch of references when mprotect is enabled. * Fix tramposed calloc arguments. * Fix crash of ulp packer on empty lines. - Disabled ptrace_scope through aaa_base-enable-ptrace package (bsc#1221763). - Update package with libpulp-0.3.4: * Add debuginfo into ulp extract. - Disabled ptrace_scope when building the package (bsc#1221763). - Update package with libpulp-0.3.3: * Fixed a race condition when process list is empty. * Removed "Unable to get section data" error message (bsc#1223306). * Bumped asunsafe_conversion attempts from 100 to 2000. * Fixed banner test on clang-18. * Check if ptrace_scope is enabled when attempting a ptrace operation (bsc#1221763). - Update package with libpulp-0.3.1: * Add timestamp information on `ulp patches`. ulp-macros: - Initial release. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-SLE-Micro-6.0-58 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-202520014-1/ Link for SUSE-SU-2025:20014-1 https://lists.suse.com/pipermail/sle-security-updates/2025-June/021360.html E-Mail link for SUSE-SU-2025:20014-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1220523 SUSE Bug 1220523 https://bugzilla.suse.com/1220690 SUSE Bug 1220690 https://bugzilla.suse.com/1220693 SUSE Bug 1220693 https://bugzilla.suse.com/1220696 SUSE Bug 1220696 https://bugzilla.suse.com/1221365 SUSE Bug 1221365 https://bugzilla.suse.com/1221751 SUSE Bug 1221751 https://bugzilla.suse.com/1221752 SUSE Bug 1221752 https://bugzilla.suse.com/1221753 SUSE Bug 1221753 https://bugzilla.suse.com/1221760 SUSE Bug 1221760 https://bugzilla.suse.com/1221763 SUSE Bug 1221763 https://bugzilla.suse.com/1221786 SUSE Bug 1221786 https://bugzilla.suse.com/1221787 SUSE Bug 1221787 https://bugzilla.suse.com/1221821 SUSE Bug 1221821 https://bugzilla.suse.com/1221822 SUSE Bug 1221822 https://bugzilla.suse.com/1221824 SUSE Bug 1221824 https://bugzilla.suse.com/1221827 SUSE Bug 1221827 https://bugzilla.suse.com/1222548 SUSE Bug 1222548 https://bugzilla.suse.com/1222899 SUSE Bug 1222899 https://bugzilla.suse.com/1223306 SUSE Bug 1223306 https://bugzilla.suse.com/1223336 SUSE Bug 1223336 https://bugzilla.suse.com/1223428 SUSE Bug 1223428 https://bugzilla.suse.com/1224388 SUSE Bug 1224388 https://bugzilla.suse.com/1225291 SUSE Bug 1225291 https://bugzilla.suse.com/1225551 SUSE Bug 1225551 https://bugzilla.suse.com/1226463 SUSE Bug 1226463 https://bugzilla.suse.com/1227138 SUSE Bug 1227138 https://bugzilla.suse.com/1229465 SUSE Bug 1229465 https://www.suse.com/security/cve/CVE-2024-2511/ SUSE CVE CVE-2024-2511 page https://www.suse.com/security/cve/CVE-2024-4603/ SUSE CVE CVE-2024-4603 page https://www.suse.com/security/cve/CVE-2024-4741/ SUSE CVE CVE-2024-4741 page https://www.suse.com/security/cve/CVE-2024-5535/ SUSE CVE CVE-2024-5535 page https://www.suse.com/security/cve/CVE-2024-6119/ SUSE CVE CVE-2024-6119 page SUSE Linux Micro 6.0 jitterentropy-devel-3.4.1-3.1 libjitterentropy3-3.4.1-3.1 libopenssl-3-devel-3.1.4-6.1 libopenssl-3-fips-provider-3.1.4-6.1 libopenssl3-3.1.4-6.1 libpulp-tools-0.3.5-1.1 libpulp0-0.3.5-1.1 openssl-3-3.1.4-6.1 jitterentropy-devel-3.4.1-3.1 as a component of SUSE Linux Micro 6.0 libjitterentropy3-3.4.1-3.1 as a component of SUSE Linux Micro 6.0 libopenssl-3-devel-3.1.4-6.1 as a component of SUSE Linux Micro 6.0 libopenssl-3-fips-provider-3.1.4-6.1 as a component of SUSE Linux Micro 6.0 libopenssl3-3.1.4-6.1 as a component of SUSE Linux Micro 6.0 libpulp-tools-0.3.5-1.1 as a component of SUSE Linux Micro 6.0 libpulp0-0.3.5-1.1 as a component of SUSE Linux Micro 6.0 openssl-3-3.1.4-6.1 as a component of SUSE Linux Micro 6.0 Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue. CVE-2024-2511 SUSE Linux Micro 6.0:jitterentropy-devel-3.4.1-3.1 SUSE Linux Micro 6.0:libjitterentropy3-3.4.1-3.1 SUSE Linux Micro 6.0:libopenssl-3-devel-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl-3-fips-provider-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl3-3.1.4-6.1 SUSE Linux Micro 6.0:libpulp-tools-0.3.5-1.1 SUSE Linux Micro 6.0:libpulp0-0.3.5-1.1 SUSE Linux Micro 6.0:openssl-3-3.1.4-6.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/support/update/announcement/2025/suse-su-202520014-1/ https://www.suse.com/security/cve/CVE-2024-2511.html CVE-2024-2511 https://bugzilla.suse.com/1222548 SUSE Bug 1222548 Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks. An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue. CVE-2024-4603 SUSE Linux Micro 6.0:jitterentropy-devel-3.4.1-3.1 SUSE Linux Micro 6.0:libjitterentropy3-3.4.1-3.1 SUSE Linux Micro 6.0:libopenssl-3-devel-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl-3-fips-provider-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl3-3.1.4-6.1 SUSE Linux Micro 6.0:libpulp-tools-0.3.5-1.1 SUSE Linux Micro 6.0:libpulp0-0.3.5-1.1 SUSE Linux Micro 6.0:openssl-3-3.1.4-6.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/support/update/announcement/2025/suse-su-202520014-1/ https://www.suse.com/security/cve/CVE-2024-4603.html CVE-2024-4603 https://bugzilla.suse.com/1224388 SUSE Bug 1224388 Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. CVE-2024-4741 SUSE Linux Micro 6.0:jitterentropy-devel-3.4.1-3.1 SUSE Linux Micro 6.0:libjitterentropy3-3.4.1-3.1 SUSE Linux Micro 6.0:libopenssl-3-devel-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl-3-fips-provider-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl3-3.1.4-6.1 SUSE Linux Micro 6.0:libpulp-tools-0.3.5-1.1 SUSE Linux Micro 6.0:libpulp0-0.3.5-1.1 SUSE Linux Micro 6.0:openssl-3-3.1.4-6.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/support/update/announcement/2025/suse-su-202520014-1/ https://www.suse.com/security/cve/CVE-2024-4741.html CVE-2024-4741 https://bugzilla.suse.com/1225551 SUSE Bug 1225551 https://bugzilla.suse.com/1225552 SUSE Bug 1225552 Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available. CVE-2024-5535 SUSE Linux Micro 6.0:jitterentropy-devel-3.4.1-3.1 SUSE Linux Micro 6.0:libjitterentropy3-3.4.1-3.1 SUSE Linux Micro 6.0:libopenssl-3-devel-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl-3-fips-provider-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl3-3.1.4-6.1 SUSE Linux Micro 6.0:libpulp-tools-0.3.5-1.1 SUSE Linux Micro 6.0:libpulp0-0.3.5-1.1 SUSE Linux Micro 6.0:openssl-3-3.1.4-6.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/support/update/announcement/2025/suse-su-202520014-1/ https://www.suse.com/security/cve/CVE-2024-5535.html CVE-2024-5535 https://bugzilla.suse.com/1227138 SUSE Bug 1227138 https://bugzilla.suse.com/1227147 SUSE Bug 1227147 https://bugzilla.suse.com/1227233 SUSE Bug 1227233 Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process. Impact summary: Abnormal termination of an application can a cause a denial of service. Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `otherName` subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program. Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address. TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. CVE-2024-6119 SUSE Linux Micro 6.0:jitterentropy-devel-3.4.1-3.1 SUSE Linux Micro 6.0:libjitterentropy3-3.4.1-3.1 SUSE Linux Micro 6.0:libopenssl-3-devel-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl-3-fips-provider-3.1.4-6.1 SUSE Linux Micro 6.0:libopenssl3-3.1.4-6.1 SUSE Linux Micro 6.0:libpulp-tools-0.3.5-1.1 SUSE Linux Micro 6.0:libpulp0-0.3.5-1.1 SUSE Linux Micro 6.0:openssl-3-3.1.4-6.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/support/update/announcement/2025/suse-su-202520014-1/ https://www.suse.com/security/cve/CVE-2024-6119.html CVE-2024-6119 https://bugzilla.suse.com/1229465 SUSE Bug 1229465