CVE-2023-0286

published 8 Feb 2023 · updated 14 Oct 2026

X.400 address type confusion in X.509 GeneralName

8.4HighCVSS 7.4EPSS 62%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 62%. Fixed in OpenSSL 1.0.2zg, OpenSSL 1.1.1t and OpenSSL 3.0.8.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
OpenSSLOpenSSL>=1.0.2 <1.0.2zg, >=1.1.1 <1.1.1t, >=3.0.0 <3.0.81.0.2zg, 1.1.1t, 3.0.8

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in OpenSSL, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-0286 severity on Zeptric[![CVE-2023-0286](https://zeptric.io/badge/cve/CVE-2023-0286.svg)](https://zeptric.io/cve/CVE-2023-0286)