Skip to content
Noroxi
CVE-2023-0286· NVD / CVE Program· CNA openssl

X.400 address type confusion in X.509 GeneralName

Noroxi assessment

Priority: Plan (action score 50/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 71.2% (FIRST EPSS); higher than 99.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: OpenSSL OpenSSL 3.0.8.
  • Mentioned 6 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to OpenSSL OpenSSL 3.0.8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.4 · v3.1—No exploit Fix available
Published
Feb 8, 2023
Updated
Oct 14, 2026
EPSS
71.2% · 99th percentile

Report tools

JSON

Action score

50

Plan

Add it to your regular patch cycle.

CVSS
29 / 40 · 7.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
21 / 30 · 71.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.4
CNA · openssl
7.4
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-0286

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl
stormshieldstormshield management center
stormshieldstormshield network security

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openssl openssl1.0.2 and later · before 1.0.2zg
  • openssl openssl1.1.1 and later · before 1.1.1t
  • openssl openssl3.0.0 and later · before 3.0.8
  • stormshield stormshield management centerbefore 3.3.3
  • stormshield stormshield network security2.7.0 and later · before 2.7.11
  • stormshield stormshield network security2.8.0 and later · before 3.7.34
  • stormshield stormshield network security3.8.0 and later · before 3.11.22
  • stormshield stormshield network security4.0.0 and later · before 4.3.16
  • stormshield stormshield network security4.4.0 and later · before 4.6.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 3.0.0 and later · before 3.0.8affected · semver
    • 1.1.1 and later · before 1.1.1taffected
    • 1.0.2 and later · before 1.0.2zgaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8compat-openssl10before 1:1.0.2o-4.el8_10.11:1.0.2o-4.el8_10.1
AlmaLinux:8edk2-aarch64before 20220126gitbb1bba3d77-4.el820220126gitbb1bba3d77-4.el8
AlmaLinux:8edk2-ovmfbefore 20220126gitbb1bba3d77-4.el820220126gitbb1bba3d77-4.el8
AlmaLinux:8opensslbefore 1:1.1.1k-9.el8_71:1.1.1k-9.el8_7
AlmaLinux:8openssl-develbefore 1:1.1.1k-9.el8_71:1.1.1k-9.el8_7
AlmaLinux:8openssl-libsbefore 1:1.1.1k-9.el8_71:1.1.1k-9.el8_7
AlmaLinux:8openssl-perlbefore 1:1.1.1k-9.el8_71:1.1.1k-9.el8_7
AlmaLinux:9compat-openssl11before 1:1.1.1k-5.el9_6.11:1.1.1k-5.el9_6.1
AlmaLinux:9edk2-aarch64before 20221207gitfff6d81270b5-9.el9_220221207gitfff6d81270b5-9.el9_2
AlmaLinux:9edk2-ovmfbefore 20221207gitfff6d81270b5-9.el9_220221207gitfff6d81270b5-9.el9_2
AlmaLinux:9edk2-toolsbefore 20221207gitfff6d81270b5-9.el9_220221207gitfff6d81270b5-9.el9_2
AlmaLinux:9edk2-tools-docbefore 20221207gitfff6d81270b5-9.el9_220221207gitfff6d81270b5-9.el9_2
AlmaLinux:9opensslbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
AlmaLinux:9openssl-develbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
AlmaLinux:9openssl-libsbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
AlmaLinux:9openssl-perlbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Alpine:v3.14opensslfrom 1.0.2 · before 1.1.1t-r01.1.1t-r0
Alpine:v3.15openssl3before 3.0.8-r03.0.8-r0
Alpine:v3.17opensslfrom 1.0.2 · before 3.0.8-r03.0.8-r0
crates.ioopenssl-srcfrom 0.0.0-0 · before 111.25.0111.25.0
crates.ioopenssl-srcfrom 300.0.0 · before 300.0.12300.0.12
crates.ioopenssl-srcbefore 111.25.0111.25.0
Debian:10opensslbefore 1.1.1n-0+deb10u41.1.1n-0+deb10u4
Debian:11opensslbefore 1.1.1n-0+deb11u41.1.1n-0+deb11u4

+96

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2022-4450Feb 8, 2023 · Double free after calling PEM_read_bio_ex
    39Monitor
  • ← EarlierCVE-2023-0215Feb 8, 2023 · Use-after-free following BIO_new_NDEF
    32Monitor
  • Later →CVE-2022-4203Feb 24, 2023 · X.509 Name Constraints Read Buffer Overflow
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.0.8Vendor (CNA)
almalinux:compat-openssl101:1.0.2o-4.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:compat-openssl111:1.1.1k-5.el9_6.1 · AlmaLinux:9Package registry (OSV)
almalinux:edk2-aarch6420221207gitfff6d81270b5-9.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:edk2-ovmf20221207gitfff6d81270b5-9.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:edk2-tools20221207gitfff6d81270b5-9.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:edk2-tools-doc20221207gitfff6d81270b5-9.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:openssl1:3.0.1-47.el9_1 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-devel1:3.0.1-47.el9_1 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-libs1:3.0.1-47.el9_1 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-perl1:3.0.1-47.el9_1 · AlmaLinux:9Package registry (OSV)
alpine:openssl1.1.1t-r0 · Alpine:v3.14Package registry (OSV)
alpine:openssl33.0.8-r0 · Alpine:v3.15Package registry (OSV)
crates.io:openssl-src111.25.0Package registry (OSV)
crates.io:openssl-src300.0.12Package registry (OSV)
debian:openssl3.0.8-1 · Debian:12Package registry (OSV)
opensuse:oci-cli3.23.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:openssl-1_0_01.0.2p-150000.3.65.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:openssl-1_11.1.1d-150200.11.57.1 · openSUSE:Leap Micro 5.2Package registry (OSV)
opensuse:openssl-1_1-livepatches0.1-150400.3.3.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:openssl-33.0.1-150400.4.17.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:python3103.10.12-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3113.11.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3123.12.0b3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python383.8.17-1.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python393.9.17-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-grpc1.52.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:cryptography39.0.1Package registry (OSV)
red hat:edk20:20220126gitbb1bba3d77-3.el9_0.2 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:edk2-aarch640:20220126gitbb1bba3d77-3.el9_0.2 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)

+20

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records