OpenSSL up to 1.0.2zf/1.1.1s/3.0.7 X.400 Address type confusion

Summaryinfo

A vulnerability has been found in OpenSSL up to 1.0.2zf/1.1.1s/3.0.7 and classified as problematic. This affects an unknown function of the component X.400 Address Handler. The manipulation leads to type confusion. This vulnerability is traded as CVE-2023-0286. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in OpenSSL up to 1.0.2zf/1.1.1s/3.0.7 (Network Encryption Software). This issue affects an unknown part of the component X.400 Address Handler. The manipulation with an unknown input leads to a type confusion vulnerability. Using CWE to declare the problem leads to CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 02/07/2023 by David Benjamin. The advisory is shared at openssl.org. The identification of this vulnerability is CVE-2023-0286. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/05/2025).

The vulnerability scanner Nessus provides a plugin with the ID 211573 (Oracle Linux 9 : openssl / and / openssl-fips-provider (ELSA-2024-9333)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.0.2zg, 1.1.1t or 3.0.8 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (211573). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Network Encryption Software

Name

• OpenSSL

Version

• 1.0.2za
• 1.0.2zb
• 1.0.2zc
• 1.0.2zd
• 1.0.2ze
• 1.0.2zf
• 1.1.1
• 1.1.1a
• 1.1.1b
• 1.1.1c
• 1.1.1d
• 1.1.1e
• 1.1.1f
• 1.1.1g
• 1.1.1h
• 1.1.1i
• 1.1.1j
• 1.1.1k
• 1.1.1l
• 1.1.1m
• 1.1.1n
• 1.1.1o
• 1.1.1p
• 1.1.1q
• 1.1.1r
• 1.1.1s
• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4
• 3.0.5
• 3.0.6
• 3.0.7

License

• open-source

Website

• Product: https://www.openssl.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion