Memory disclosure or crash via X.400 type confusion
Published Feb 8, 2023 · Updated Nov 4, 2025
Type confusion in X.509 GeneralName processing in OpenSSL allows remote attackers to read memory or crash applications through crafted X.400 addresses. GENERAL_NAME_cmp treats an x400Address parsed as ASN1_STRING as ASN1_TYPE, allowing attacker-controlled pointers to reach memcmp. CRL checking must be enabled, and exploitation generally requires control of both the certificate chain and CRL.
Summary
What happened
Type confusion in X.509 GeneralName processing in OpenSSL allows remote attackers to read memory or crash applications through crafted X.400 addresses. GENERAL_NAME_cmp treats an x400Address parsed as ASN1_STRING as ASN1_TYPE, allowing attacker-controlled pointers to reach memcmp. CRL checking must be enabled, and exploitation generally requires control of both the certificate chain and CRL.
The record
- CVE
- CVE-2023-0286
- Published
- Feb 8, 2023
- Updated
- Nov 4, 2025
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-843, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.2 <1.0.2zg
- Affected versionversion=1.1.1 <1.1.1t
- Affected versionversion=3.0.0 <3.0.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo