Access of Resource Using Incompatible Type ('Type Confusion') Affecting openssl-libs package, versions <2:1.1.1k-9.ksplice1.el8_7


0.0
high

Snyk CVSS

    Attack Complexity High
    Confidentiality High
    Availability High

    Threat Intelligence

    EPSS 0.21% (59th percentile)
Expand this section
NVD
7.4 high
Expand this section
SUSE
7.4 high
Expand this section
Red Hat
7.4 high

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-ORACLE8-OPENSSLLIBS-3368722
  • published 1 Mar 2023
  • disclosed 8 Feb 2023

How to fix?

Upgrade Oracle:8 openssl-libs to version 2:1.1.1k-9.ksplice1.el8_7 or higher.
This issue was patched in ELSA-2023-12213.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl-libs package and not the openssl-libs package as distributed by Oracle. See How to fix? for Oracle:8 relevant fixed versions and status.

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.