Skip to content
Noroxi
CVE-2022-4203· NVD / CVE Program· CNA openssl

X.509 Name Constraints Read Buffer Overflow

Noroxi assessment

Priority: Monitor (action score 19/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: 1.3% (FIRST EPSS); higher than 71.7% of all records.
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: OpenSSL OpenSSL 3.0.8.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. 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

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

MediumCVSS 4.9 · v3.1—No exploit Fix available
Published
Feb 24, 2023
Updated
Jun 17, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-2022-4203

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

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 openssl3.0.0 and later · before 3.0.8

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

Package-level exposure

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

EcosystemPackageAffected rangeFix
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.15openssl3before 3.0.8-r03.0.8-r0
Alpine:v3.17opensslfrom 3.0.0 · before 3.0.8-r03.0.8-r0
crates.ioopenssl-srcfrom 300.0.0 · before 300.0.12300.0.12
Debian:12opensslbefore 3.0.8-13.0.8-1
openSUSE:Tumbleweedopenssl-3before 3.0.8-1.13.0.8-1.1
Red Hat:enterprise_linux:9::appstreamopenssl-debuginfobefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:enterprise_linux:9::appstreamopenssl-debugsourcebefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:enterprise_linux:9::appstreamopenssl-develbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:enterprise_linux:9::appstreamopenssl-libs-debuginfobefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:enterprise_linux:9::appstreamopenssl-perlbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:enterprise_linux:9::baseosopensslbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:enterprise_linux:9::baseosopenssl-libsbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1
Red Hat:rhel_eus:9.0::appstreamopenssl-debuginfobefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Red Hat:rhel_eus:9.0::appstreamopenssl-debugsourcebefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Red Hat:rhel_eus:9.0::appstreamopenssl-develbefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Red Hat:rhel_eus:9.0::appstreamopenssl-libs-debuginfobefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Red Hat:rhel_eus:9.0::appstreamopenssl-perlbefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Red Hat:rhel_eus:9.0::baseosopensslbefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Red Hat:rhel_eus:9.0::baseosopenssl-libsbefore 1:3.0.1-46.el9_01:3.0.1-46.el9_0
Rocky Linux:9opensslbefore 1:3.0.1-47.el9_11:3.0.1-47.el9_1

+2

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-2023-0215Feb 8, 2023 · Use-after-free following BIO_new_NDEF
    32Monitor
  • ← EarlierCVE-2023-0286Feb 8, 2023 · X.400 address type confusion in X.509 GeneralName
    50Plan
  • Later →CVE-2023-0464Mar 22, 2023 · Excessive Resource Usage Verifying X.509 Policy Constraints
    31Monitor

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: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:openssl3.0.8-r0 · Alpine:v3.17Package registry (OSV)
alpine:openssl33.0.8-r0 · Alpine:v3.15Package registry (OSV)
crates.io:openssl-src300.0.12Package registry (OSV)
debian:openssl3.0.8-1 · Debian:12Package registry (OSV)
opensuse:openssl-33.0.1-150400.4.17.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:openssl1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:openssl-debuginfo1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-debugsource1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-devel1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-libs1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:openssl-libs-debuginfo1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-perl1:3.0.1-47.el9_1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:openssl1:3.0.1-47.el9_1 · Rocky Linux:9Package registry (OSV)
suse:openssl-33.0.1-150400.4.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package registry (OSV)

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.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

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

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

All records