NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2023-0286 — openssl-src

HIGH

CVE-2023-0286 is a high-severity (CVSS 7.4) CWE-843 vulnerability in openssl-src. EPSS puts its 30-day exploitation probability at 69.3% (99th percentile). A fix is available for openssl-src — see the affected versions and patch details below.

X.400 address type confusion in X.509 GeneralName

Also known asGHSA-x4qr-2fvf-3mr5PYSEC-2026-800RUSTSEC-2023-0006
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-0286.

EPSS Exploitation Probability

via FIRST.org ↗
69.3%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
50.9%66.2%81.6%97.0%88.3%69.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🦀openssl-src🦀openssl-src🐍cryptography

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io, PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioopenssl-srcall versions111.25.0cargo update -p openssl-src --precise 111.25.0
🦀crates.ioopenssl-src≥ 300.0.0&&< 300.0.12300.0.12cargo update -p openssl-src --precise 300.0.12
🐍PyPIcryptography≥ 0.8.1&&< 39.0.139.0.1pip install --upgrade 'cryptography==39.0.1'

Affected Products

3 products · 9 configurations
Application
opensslopenssl
≥ 3.0.0 && < 3.0.8
range
Application
stormshield management centerstormshield
< 3.3.3
range
Application
stormshield network securitystormshield
≥ 4.4.0 && < 4.6.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-src, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update openssl-src to 111.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-0286 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

For shim in Red Hat Enterprise Linux 8 & 9, is not affected as shim doesn't support any CRL processing.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2023-0286 (CC BY 4.0)
ProductFixed inAdvisory
JBCS httpd 2.4.51.sp2opensslRHSA-2023:3355
JBoss Core Services for RHEL 8jbcs-httpd24-openssl-1:1.1.1k-14.el8jbcsRHSA-2023:3354
Red Hat Enterprise Linux 6 Extended Lifecycle Supportopenssl-0:1.0.1e-61.el6_10RHSA-2023:1438
Red Hat Enterprise Linux 7openssl-1:1.0.2k-26.el7_9RHSA-2023:1335
Red Hat Enterprise Linux 7.7 Advanced Update Supportopenssl-1:1.0.2k-21.el7_7.1RHSA-2024:5136
Red Hat Enterprise Linux 8edk2-0:20220126gitbb1bba3d77-4.el8RHSA-2023:2932
Red Hat Enterprise Linux 8compat-openssl10-1:1.0.2o-4.el8_10.1RHSA-2025:7895
Red Hat Enterprise Linux 8openssl-1:1.1.1k-9.el8_7RHSA-2023:1405

Frequently Asked Questions

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 mem
O3 Security · Impact-Aware SCA

Is CVE-2023-0286 in your dependencies?

Find it across crates.io, PyPI, including transitive dependencies.

CVE-2023-0286: openssl-src DoS — Fixed in 111.25.0