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.

Project Subscriptions

Vendors Products
Openssl Subscribe
Openssl Subscribe
Enterprise Linux Subscribe
Jboss Core Services Subscribe
Jboss Enterprise Web Server Subscribe
Logging Subscribe
Rhel Aus Subscribe
Rhel E4s Subscribe
Rhel Els Subscribe
Rhel Eus Subscribe
Rhel Tus Subscribe
Rhev Hypervisor Subscribe
Stormshield Subscribe
Stormshield Management Center Subscribe
Stormshield Network Security Subscribe
Advisories
Source ID Title
Debian DLA Debian DLA DLA-3325-1 openssl security update
Debian DSA Debian DSA DSA-5343-1 openssl security update
Github GHSA Github GHSA GHSA-x4qr-2fvf-3mr5 Vulnerable OpenSSL included in cryptography wheels
Ubuntu USN Ubuntu USN USN-5844-1 OpenSSL vulnerabilities
Ubuntu USN Ubuntu USN USN-5845-1 OpenSSL vulnerabilities
Ubuntu USN Ubuntu USN USN-5845-2 OpenSSL vulnerabilities
Ubuntu USN Ubuntu USN USN-6564-1 Node.js vulnerabilities
Ubuntu USN Ubuntu USN USN-7894-1 EDK II vulnerabilities
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Tue, 04 Nov 2025 20:30:00 +0000

Type Values Removed Values Added
References

Wed, 16 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 0.89545}

epss

{'score': 0.8964}


Fri, 11 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 0.8964}

epss

{'score': 0.89545}


Fri, 16 May 2025 02:30:00 +0000

Type Values Removed Values Added
CPEs cpe:/a:redhat:rhel_eus:9.4

Thu, 20 Mar 2025 21:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 13 Feb 2025 16:45:00 +0000

Type Values Removed Values Added
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. 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.

Thu, 12 Sep 2024 02:15:00 +0000

Type Values Removed Values Added
First Time appeared Redhat logging
CPEs cpe:/a:redhat:logging:5.9::el9
Vendors & Products Redhat logging

Thu, 08 Aug 2024 19:00:00 +0000

Type Values Removed Values Added
CPEs cpe:/o:redhat:rhel_aus:7.7

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: openssl

Published:

Updated: 2025-11-04T19:14:36.256Z

Reserved: 2023-01-13T10:40:41.259Z

Link: CVE-2023-0286

cve-icon Vulnrichment

Updated: 2025-11-04T19:14:36.256Z

cve-icon NVD

Status : Modified

Published: 2023-02-08T20:15:24.267

Modified: 2025-11-04T20:16:16.350

Link: CVE-2023-0286

cve-icon Redhat

Severity : Important

Publid Date: 2023-02-07T00:00:00Z

Links: CVE-2023-0286 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses