Medium: openssl

Issue Overview:

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)

Affected Packages:

openssl

Note:

This advisory is applicable to Amazon Linux 2 (AL2) Core repository. Visit this FAQ section for the difference between AL2 Core and AL2 Extras advisories.

Issue Correction:
Run yum update openssl to update your system.

New Packages:

aarch64:  
    openssl-1.0.2k-24.amzn2.0.7.aarch64  
    openssl-libs-1.0.2k-24.amzn2.0.7.aarch64  
    openssl-devel-1.0.2k-24.amzn2.0.7.aarch64  
    openssl-static-1.0.2k-24.amzn2.0.7.aarch64  
    openssl-perl-1.0.2k-24.amzn2.0.7.aarch64  
    openssl-debuginfo-1.0.2k-24.amzn2.0.7.aarch64  
  
i686:  
    openssl-1.0.2k-24.amzn2.0.7.i686  
    openssl-libs-1.0.2k-24.amzn2.0.7.i686  
    openssl-devel-1.0.2k-24.amzn2.0.7.i686  
    openssl-static-1.0.2k-24.amzn2.0.7.i686  
    openssl-perl-1.0.2k-24.amzn2.0.7.i686  
    openssl-debuginfo-1.0.2k-24.amzn2.0.7.i686  
  
src:  
    openssl-1.0.2k-24.amzn2.0.7.src  
  
x86_64:  
    openssl-1.0.2k-24.amzn2.0.7.x86_64  
    openssl-libs-1.0.2k-24.amzn2.0.7.x86_64  
    openssl-devel-1.0.2k-24.amzn2.0.7.x86_64  
    openssl-static-1.0.2k-24.amzn2.0.7.x86_64  
    openssl-perl-1.0.2k-24.amzn2.0.7.x86_64  
    openssl-debuginfo-1.0.2k-24.amzn2.0.7.x86_64  

Additional References

Red Hat: CVE-2023-0464, CVE-2023-0465, CVE-2023-0466, CVE-2023-2650

Mitre: CVE-2023-0464, CVE-2023-0465, CVE-2023-0466, CVE-2023-2650