An update for openssl is now available for openEuler-22.03-LTS-SP1 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2024-2385 Final 1.0 1.0 2024-11-15 Initial 2024-11-15 2024-11-15 openEuler SA Tool V1.0 2024-11-15 openssl security update An update for openssl is now available for openEuler-22.03-LTS-SP1 OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols. Security Fix(es): Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.(CVE-2024-9143) An update for openssl is now available for openEuler-22.03-LTS-SP1. openEuler Security has rated this update as having a security impact of medium. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Medium openssl https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2385 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2024-9143 https://nvd.nist.gov/vuln/detail/CVE-2024-9143 openEuler-22.03-LTS-SP1 openssl-1.1.1m-39.oe2203sp1.aarch64.rpm openssl-debuginfo-1.1.1m-39.oe2203sp1.aarch64.rpm openssl-debugsource-1.1.1m-39.oe2203sp1.aarch64.rpm openssl-devel-1.1.1m-39.oe2203sp1.aarch64.rpm openssl-libs-1.1.1m-39.oe2203sp1.aarch64.rpm openssl-perl-1.1.1m-39.oe2203sp1.aarch64.rpm openssl-1.1.1m-39.oe2203sp1.src.rpm openssl-1.1.1m-39.oe2203sp1.x86_64.rpm openssl-debuginfo-1.1.1m-39.oe2203sp1.x86_64.rpm openssl-debugsource-1.1.1m-39.oe2203sp1.x86_64.rpm openssl-devel-1.1.1m-39.oe2203sp1.x86_64.rpm openssl-libs-1.1.1m-39.oe2203sp1.x86_64.rpm openssl-perl-1.1.1m-39.oe2203sp1.x86_64.rpm openssl-help-1.1.1m-39.oe2203sp1.noarch.rpm Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. 2024-11-15 CVE-2024-9143 openEuler-22.03-LTS-SP1 Medium 4.3 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N openssl security update 2024-11-15 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2385