ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-0286

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName.

Published Feb 8, 2023 · catalog updated Oct 14, 2026 · There is a type

Check this week

CVE-2023-0286 is not in CISA KEV. FIRST estimates a 71.24% chance of exploitation in the next 30 days. Check whether you run There is a type.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (There is a type).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
71.24%
Remediation
Advisory link
Affected products
cpe openssl/openssl · cpe stormshield/stormshield management center · cpe stormshield/stormshield network security

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe openssl/opensslversion unspecified
  • cpe stormshield/stormshield management centerversion unspecified
  • cpe stormshield/stormshield network securityversion unspecified

How to fix CVE-2023-0286

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2023-0286 is not in CISA KEV. FIRST estimates a 71.24% chance of exploitation in the next 30 days. Check whether you run There is a type.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-843: Access of Resource Using Incompatible Type (Type Confusion). EPSS 71.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 8, 2023 · NIST NVD

    Detected

    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. W

  2. Oct 14, 2026 · NIST NVD

    Updated

    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. W

Sources

  • CVE.orgVulnerability recordCVE-2023-0286

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2023-0286

    30-day exploitation probability 71.2%

    first.org
  • NIST NVDVulnerability recordCVE-2023-0286

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.