CVE-2022-4203

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of service disruption.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-02-24 15:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 05:20 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 4.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-02-24 15:15 UTC

Last modified

2026-06-17 05:20 UTC

Exploit probability

1.4% · EPSS, next 30 days

Weakness

CWE-125 · Out-of-bounds read

Record status

Modified

Affected

• OpenSSL < 3.0.8

Attack profile CVSS 3.1 · 4.9

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-4203.md and follow it. Check whether this project is affected by CVE-2022-4203. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge