An update for edk2 is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP2 and openEuler-22.03-LTS-SP3 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2024-1238 Final 1.0 1.0 2024-03-01 Initial 2024-03-01 2024-03-01 openEuler SA Tool V1.0 2024-03-01 edk2 security update An update for edk2 is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP2 and openEuler-22.03-LTS-SP3. EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications. Security Fix(es): A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function.(CVE-2023-0464) Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function.(CVE-2023-0465) The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.(CVE-2023-0466) Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow. Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service. An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods. When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*). With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms. Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data. Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low. In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature. The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication. In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.(CVE-2023-2650) Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH 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 function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length. However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam 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 not affected by this issue.(CVE-2023-3446) Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.(CVE-2024-0727) An update for edk2 is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP2 and openEuler-22.03-LTS-SP3. openEuler Security has rated this update as having a security impact of high. 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. High edk2 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-0464 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-0465 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-0466 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-2650 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-3446 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2024-0727 https://nvd.nist.gov/vuln/detail/CVE-2023-0464 https://nvd.nist.gov/vuln/detail/CVE-2023-0465 https://nvd.nist.gov/vuln/detail/CVE-2023-0466 https://nvd.nist.gov/vuln/detail/CVE-2023-2650 https://nvd.nist.gov/vuln/detail/CVE-2023-3446 https://nvd.nist.gov/vuln/detail/CVE-2024-0727 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 edk2-debuginfo-202002-18.oe1.aarch64.rpm edk2-devel-202002-18.oe1.aarch64.rpm edk2-debugsource-202002-18.oe1.aarch64.rpm edk2-devel-202002-18.oe2003sp4.aarch64.rpm edk2-debuginfo-202002-18.oe2003sp4.aarch64.rpm edk2-debugsource-202002-18.oe2003sp4.aarch64.rpm edk2-debugsource-202011-14.oe2203.aarch64.rpm edk2-devel-202011-14.oe2203.aarch64.rpm edk2-debuginfo-202011-14.oe2203.aarch64.rpm edk2-debugsource-202011-14.oe2203sp1.aarch64.rpm edk2-debuginfo-202011-14.oe2203sp1.aarch64.rpm edk2-devel-202011-14.oe2203sp1.aarch64.rpm edk2-debugsource-202011-14.oe2203sp2.aarch64.rpm edk2-devel-202011-14.oe2203sp2.aarch64.rpm edk2-debuginfo-202011-14.oe2203sp2.aarch64.rpm edk2-debuginfo-202011-14.oe2203sp3.aarch64.rpm edk2-debugsource-202011-14.oe2203sp3.aarch64.rpm edk2-devel-202011-14.oe2203sp3.aarch64.rpm edk2-help-202002-18.oe1.noarch.rpm python3-edk2-devel-202002-18.oe1.noarch.rpm edk2-aarch64-202002-18.oe1.noarch.rpm edk2-ovmf-202002-18.oe1.noarch.rpm python3-edk2-devel-202002-18.oe2003sp4.noarch.rpm edk2-ovmf-202002-18.oe2003sp4.noarch.rpm edk2-aarch64-202002-18.oe2003sp4.noarch.rpm edk2-help-202002-18.oe2003sp4.noarch.rpm edk2-aarch64-202011-14.oe2203.noarch.rpm python3-edk2-devel-202011-14.oe2203.noarch.rpm edk2-help-202011-14.oe2203.noarch.rpm edk2-ovmf-202011-14.oe2203.noarch.rpm python3-edk2-devel-202011-14.oe2203sp1.noarch.rpm edk2-help-202011-14.oe2203sp1.noarch.rpm edk2-ovmf-202011-14.oe2203sp1.noarch.rpm edk2-aarch64-202011-14.oe2203sp1.noarch.rpm python3-edk2-devel-202011-14.oe2203sp2.noarch.rpm edk2-ovmf-202011-14.oe2203sp2.noarch.rpm edk2-aarch64-202011-14.oe2203sp2.noarch.rpm edk2-help-202011-14.oe2203sp2.noarch.rpm python3-edk2-devel-202011-14.oe2203sp3.noarch.rpm edk2-ovmf-202011-14.oe2203sp3.noarch.rpm edk2-aarch64-202011-14.oe2203sp3.noarch.rpm edk2-help-202011-14.oe2203sp3.noarch.rpm edk2-202002-18.oe1.src.rpm edk2-202002-18.oe2003sp4.src.rpm edk2-202011-14.oe2203.src.rpm edk2-202011-14.oe2203sp1.src.rpm edk2-202011-14.oe2203sp2.src.rpm edk2-202011-14.oe2203sp3.src.rpm edk2-debuginfo-202002-18.oe1.x86_64.rpm edk2-devel-202002-18.oe1.x86_64.rpm edk2-debugsource-202002-18.oe1.x86_64.rpm edk2-debugsource-202002-18.oe2003sp4.x86_64.rpm edk2-devel-202002-18.oe2003sp4.x86_64.rpm edk2-debuginfo-202002-18.oe2003sp4.x86_64.rpm edk2-debugsource-202011-14.oe2203.x86_64.rpm edk2-debuginfo-202011-14.oe2203.x86_64.rpm edk2-devel-202011-14.oe2203.x86_64.rpm edk2-devel-202011-14.oe2203sp1.x86_64.rpm edk2-debugsource-202011-14.oe2203sp1.x86_64.rpm edk2-debuginfo-202011-14.oe2203sp1.x86_64.rpm edk2-debuginfo-202011-14.oe2203sp2.x86_64.rpm edk2-debugsource-202011-14.oe2203sp2.x86_64.rpm edk2-devel-202011-14.oe2203sp2.x86_64.rpm edk2-devel-202011-14.oe2203sp3.x86_64.rpm edk2-debugsource-202011-14.oe2203sp3.x86_64.rpm edk2-debuginfo-202011-14.oe2203sp3.x86_64.rpm A security vulnerability has been identified in all supported versionsof OpenSSL related to the verification of X.509 certificate chainsthat include policy constraints. Attackers may be able to exploit thisvulnerability by creating a malicious certificate chain that triggersexponential use of computational resources, leading to a denial-of-service(DoS) attack on affected systems.Policy processing is disabled by default but can be enabled by passingthe `-policy argument to the command line utilities or by calling the`X509_VERIFY_PARAM_set1_policies() function. 2024-03-01 CVE-2023-0464 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 High 7.5 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H edk2 security update 2024-03-01 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238 Applications that use a non-default option when verifying certificates may bevulnerable to an attack from a malicious CA to circumvent certain checks.Invalid certificate policies in leaf certificates are silently ignored byOpenSSL and other certificate policy checks are skipped for that certificate.A malicious CA could use this to deliberately assert invalid certificate policiesin order to circumvent policy checking on the certificate altogether.Policy processing is disabled by default but can be enabled by passingthe `-policy argument to the command line utilities or by calling the`X509_VERIFY_PARAM_set1_policies() function. 2024-03-01 CVE-2023-0465 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 Medium 5.3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N edk2 security update 2024-03-01 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238 The function X509_VERIFY_PARAM_add0_policy() is documented toimplicitly enable the certificate policy check when doing certificateverification. However the implementation of the function does notenable the check which allows certificates with invalid or incorrectpolicies to pass the certificate verification.As suddenly enabling the policy check could break existing deployments it wasdecided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy()function.Instead the applications that require OpenSSL to perform certificatepolicy check need to use X509_VERIFY_PARAM_set1_policies() or explicitlyenable the policy check by calling X509_VERIFY_PARAM_set_flags() withthe X509_V_FLAG_POLICY_CHECK flag argument.Certificate policy checks are disabled by default in OpenSSL and are notcommonly used by applications. 2024-03-01 CVE-2023-0466 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 Medium 5.3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N edk2 security update 2024-03-01 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238 Issue summary: Processing some specially crafted ASN.1 object identifiers ordata containing them may be very slow.Impact summary: Applications that use OBJ_obj2txt() directly, or use any ofthe OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no messagesize limit may experience notable to very long delays when processing thosemessages, which may lead to a Denial of Service.An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers -most of which have no size limit. OBJ_obj2txt() may be used to translatean ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSLtype ASN1_OBJECT) to its canonical numeric text form, which are thesub-identifiers of the OBJECT IDENTIFIER in decimal form, separated byperiods.When one of the sub-identifiers in the OBJECT IDENTIFIER is very large(these are sizes that are seen as absurdly large, taking up tens or hundredsof KiBs), the translation to a decimal number in text may take a very longtime. The time complexity is O(n^2) with n being the size of thesub-identifiers in bytes (*).With OpenSSL 3.0, support to fetch cryptographic algorithms using names /identifiers in string form was introduced. This includes using OBJECTIDENTIFIERs in canonical numeric text form as identifiers for fetchingalgorithms.Such OBJECT IDENTIFIERs may be received through the ASN.1 structureAlgorithmIdentifier, which is commonly used in multiple protocols to specifywhat cryptographic algorithm should be used to sign or verify, encrypt ordecrypt, or digest passed data.Applications that call OBJ_obj2txt() directly with untrusted data areaffected, with any version of OpenSSL. If the use is for the mere purposeof display, the severity is considered low.In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME,CMS, CMP/CRMF or TS. It also impacts anything that processes X.509certificates, including simple things like verifying its signature.The impact on TLS is relatively low, because all versions of OpenSSL have a100KiB limit on the peer s certificate chain. Additionally, this onlyimpacts clients, or servers that have explicitly enabled clientauthentication.In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects,such as X.509 certificates. This is assumed to not happen in such a waythat it would cause a Denial of Service, so these versions are considerednot affected by this issue in such a way that it would be cause for concern,and the severity is therefore considered low. 2024-03-01 CVE-2023-2650 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 Medium 6.5 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H edk2 security update 2024-03-01 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238 Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH 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 function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length. However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam 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 not affected by this issue. 2024-03-01 CVE-2023-3446 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 Medium 5.3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L edk2 security update 2024-03-01 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238 Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. 2024-03-01 CVE-2024-0727 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 openEuler-22.03-LTS-SP3 Medium 5.5 AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H edk2 security update 2024-03-01 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1238