Security readout for executives and security teams
Plain-English summary
CVE-2023-0286 is an OpenSSL certificate-handling bug that can expose memory or crash an application when CRL checking is enabled. It is serious, but the attack path is narrow: the attacker generally must influence both certificate chain and CRL inputs, and affected X.400 CRL distribution points are uncommon.
Executive priority
Prioritize remediation for internet-facing services, appliances, and certificate-processing systems that perform CRL checks. The issue is not broadly easy to exploit, but OpenSSL is widely embedded, and successful exploitation can expose memory or disrupt service.
Technical view
OpenSSL misdeclared X.400 GeneralName handling: x400Address was parsed as ASN1_STRING but later treated as ASN1_TYPE in GENERAL_NAME_cmp. With X509_V_FLAG_CRL_CHECK enabled, crafted certificate and CRL inputs may cause arbitrary pointer reads through memcmp, creating confidentiality and denial-of-service impact.
Likely exposure
Exposure is most likely in products or applications using OpenSSL 3.0, 1.1.1, or 1.0.2 branches with CRL checking enabled, especially custom code that retrieves CRLs over a network. Systems relying only on default TLS validation paths may be less exposed, based on the source description.
Exploitation context
The bundle does not show CISA KEV status or cited evidence of active exploitation. The CVSS vector is network-reachable with no privileges or user interaction, but attack complexity is high because control of certificate chain and CRL inputs is usually required.
Researcher notes
Focus triage on OpenSSL consumers that compare X.509 GeneralName values during CRL checking. The uncommon X.400 CRL distribution point condition narrows exposure, but custom CRL retrieval logic increases practical risk. Do not assume every OpenSSL-linked service is reachable through this bug.
Mitigation direction
- Upgrade OpenSSL to 3.0.8, 1.1.1t, or applicable 1.0.2zg fixes.
- Apply OS, appliance, and distribution updates that backport the OpenSSL fix.
- Review applications that enable CRL checking and custom network CRL retrieval.
- Follow vendor guidance for affected packaged products and appliances.
- Prioritize replacement or isolation for unsupported OpenSSL deployments.
Validation and detection
- Inventory OpenSSL and LibreSSL versions across servers, containers, appliances, and embedded products.
- Confirm whether applications set X509_V_FLAG_CRL_CHECK or perform CRL validation.
- Identify code paths that fetch CRLs from attacker-influenced network locations.
- Verify patched library versions or vendor backport advisories are installed.
- Retest certificate validation workflows after updating crypto libraries.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-843: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-0286 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H2.25.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- OpenSSL AdvisoryCVE reference · vendor-advisory
- 3.0.8 git commitCVE reference · patch
- 1.1.1t git commitCVE reference · patch
- 1.0.2zg patch (premium)CVE reference · patch
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x509.patch.sigCVE reference
- https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txtCVE reference
- https://security.gentoo.org/glsa/202402-08CVE reference
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Access of Resource Using Incompatible Type ('Type Confusion')
Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
