CVE-2023-0286

X.400 address type confusion in X.509 GeneralName

HIGH
7.4
CVSS Score
Published: February 8, 2023 at 07:01 PM UTC
Updated: October 14, 2026 at 08:17 PM UTC
3 products affected across 2 vendorsOpenSSLNetwork SecurityStormshield Management Center

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 69%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions1.0.2 ≤ v < 1.0.2zg1.1.1 ≤ v < 1.1.1t3.0.0 ≤ v < 3.0.81.0.21.1.13.0.0
Affected range stops below 1.0.2zg, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1t, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.8, so it looks safe — our inference, not a vendor statement
2.7.0 ≤ v < 2.7.112.8.0 ≤ v < 3.7.343.8.0 ≤ v < 3.11.224.0.0 ≤ v < 4.3.164.4.0 ≤ v < 4.6.3
Affected range stops below 2.7.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.11.22, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.7.34, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.3, so it looks safe — our inference, not a vendor statement
All versionsv < 3.3.3
Affected range stops below 3.3.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.4HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-843

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card