# CVE-2023-0286: X.400 address type confusion in X.509 GeneralName

> Type confusion in OpenSSL allows attackers to read memory or cause denial of service when CRL checking is enabled.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2023
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2023-0286, ALSA-2025:7895, ALSA-2025:7937, AZL-13564, AZL-13701, AZL-37614, AZL-37883, CLEANSTART-2026-ZR23634, CLSA-2025-1764692769, CLSA-2026-1772151046, DEBIAN-CVE-2023-0286, GHSA-x4qr-2fvf-3mr5, JLSEC-2026-234, MINI-5983-xgxh-x42w, OESA-2023-1121, PYSEC-2026-800, RHSA-2023:1335, RHSA-2023:1437, RHSA-2023:1438, RHSA-2023:1439, RHSA-2023:1440, RHSA-2023:1441, RHSA-2023:2022, RHSA-2023:4124, RHSA-2023:4252, RHSA-2024:5136, RHSA-2025:7733, RHSA-2025:7895, RHSA-2025:7937, RLSA-2025:7895, RLSA-2025:7937, ROOT-APP-PYPI-CVE-2023-0286, RUSTSEC-2023-0006, SUSE-SU-2023:0482-1, UBUNTU-CVE-2023-0286, openSUSE-SU-2024:12787-1, openSUSE-SU-2024:12794-1, openSUSE-SU-2024:13956-1, openSUSE-SU-2025:14821-1, openSUSE-SU-2026:10348-1

## What is CVE-2023-0286?

CVE-2023-0286 is a high-severity memory corruption vulnerability in Openssl Openssl, published on 8 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2023-0286?

8 open source packages ship an affected version, including openssl-src and cryptography. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl-src` | crates.io | All versions | 111.25.0 |
| `openssl-src` | crates.io | All versions | 111.25.0 |
| `openssl-src` | crates.io | From 0.0.0-0 | 111.25.0, 300.0.12 |
| `openssl-src` | crates.io | From 300.0.0 | 300.0.12 |
| `openssl-src` | crates.io | From 300.0.0 | 300.0.12 |
| `cryptography` | PyPI | From 0.8.1 | 39.0.1 |
| `cryptography` | PyPI | From 0.8.1 | 39.0.1 |
| `cryptography` | PyPI | From 0.8.1 | 39.0.1 |
| `compat-openssl10` | AlmaLinux:8 | All versions | 1:1.0.2o-4.el8_10.1 |
| `compat-openssl11` | AlmaLinux:9 | All versions | 1:1.1.1k-5.el9_6.1 |
| `openssl` | Red Hat:enterprise_linux:7::client | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-devel` | Red Hat:enterprise_linux:7::client | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-libs` | Red Hat:enterprise_linux:7::client | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-perl` | Red Hat:enterprise_linux:7::client | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-static` | Red Hat:enterprise_linux:7::client | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-perl` | Red Hat:enterprise_linux:7::computenode | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-static` | Red Hat:enterprise_linux:7::computenode | All versions | 1:1.0.2k-26.el7_9 |
| `openssl` | Red Hat:enterprise_linux:7::server | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-devel` | Red Hat:enterprise_linux:7::server | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-libs` | Red Hat:enterprise_linux:7::server | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-perl` | Red Hat:enterprise_linux:7::server | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-static` | Red Hat:enterprise_linux:7::server | All versions | 1:1.0.2k-26.el7_9 |
| `openssl` | Red Hat:enterprise_linux:7::workstation | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-perl` | Red Hat:enterprise_linux:7::workstation | All versions | 1:1.0.2k-26.el7_9 |
| `openssl-static` | Red Hat:enterprise_linux:7::workstation | All versions | 1:1.0.2k-26.el7_9 |
| `compat-openssl10` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.0.2o-4.el8_10.1 |
| `compat-openssl10-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.0.2o-4.el8_10.1 |
| `compat-openssl10-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.0.2o-4.el8_10.1 |
| `compat-openssl11` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_6.1 |
| `compat-openssl11-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_6.1 |
| `compat-openssl11-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_6.1 |
| `openssl` | Red Hat:rhel_aus:7.7::server | All versions | 1:1.0.2k-21.el7_7.1 |
| `openssl-debuginfo` | Red Hat:rhel_aus:7.7::server | All versions | 1:1.0.2k-21.el7_7.1 |

Products: Openssl Openssl, Stormshield Stormshield Management Center, Stormshield Stormshield Network Security.

## How do I fix CVE-2023-0286?

Upgrade openssl-src to a fixed version for your release line: 111.25.0 or 300.0.12.

## Is CVE-2023-0286 being exploited?

There is no known exploitation of CVE-2023-0286 in the wild and no public exploit code.

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0286 and fix it if it is affected.

What it is: CVE-2023-0286 is a high-severity memory corruption vulnerability in Openssl Openssl, published on 8 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0286 in the wild and no public exploit code.

Affected packages and fixed versions:
- openssl-src (crates.io): affected all versions; fixed in 111.25.0
- openssl-src (crates.io): affected all versions; fixed in 111.25.0
- openssl-src (crates.io): affected from 0.0.0-0; fixed in 111.25.0, 300.0.12
- openssl-src (crates.io): affected from 300.0.0; fixed in 300.0.12
- openssl-src (crates.io): affected from 300.0.0; fixed in 300.0.12
- cryptography (PyPI): affected from 0.8.1; fixed in 39.0.1
- cryptography (PyPI): affected from 0.8.1; fixed in 39.0.1
- cryptography (PyPI): affected from 0.8.1; fixed in 39.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-0286/ (Markdown: https://insights.sbomify.com/CVE-2023-0286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-0286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-0286
- OSV: https://osv.dev/vulnerability/CVE-2023-0286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-0286/
Summaries are generated and may contain mistakes; the official description above is the record.
