CVE-2023-0286
HIGHEPSS 99th pctlDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 99% of all known CVEs.
References
Related Vulnerabilities
Other CWE-843 (Type Confusion) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2011-0611 | High | 8.8 | 99% | KEV | Fix |
| CVE-2012-0507 | Critical | 9.8 | 98% | KEV + Ransom | - |
| CVE-2017-8291 | High | 7.8 | 97% | KEV | Fix |
| CVE-2021-21224 | High | 8.8 | 84% | KEV | Fix |
| CVE-2019-0752 | High | 7.5 | 82% | KEV + Ransom | - |
| CVE-2017-0037 | High | 8.1 | 80% | KEV | - |
Common questions
How do I fix CVE-2023-0286?
Published advisories record a fix for 204 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2023-0286 being actively exploited?
Not that we know of. CVE-2023-0286 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 59.5% is the estimated probability that it will be exploited in the next 30 days. That is higher than 99% of all scored CVEs.
How severe is CVE-2023-0286?
CVE-2023-0286 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2023-0286 affect?
Published advisories record a fix for openssl (Debian), compat-openssl10 (Rocky), compat-openssl10 (Red Hat / RHEL), compat-openssl10-debuginfo (Rocky), and 200 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2023-0286
Markdown
[](https://tridentstack.com/cve/CVE-2023-0286)HTML
<a href="https://tridentstack.com/cve/CVE-2023-0286"><img src="https://tridentstack.com/cve/badge/CVE-2023-0286.svg" alt="CVE-2023-0286"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-11-04.