CVE-2022-3786

What it is

A 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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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 without logging in. High risk of service disruption.

Exploit odds

92.5% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

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

Timeline

1. 2022-11-01 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2022-11-01 18:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 05:00 UTC Last updatedMost recent change to the record

Why it ranks here

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

Details

Published

2022-11-01 18:15 UTC

Last modified

2026-06-17 05:00 UTC

Exploit probability

92.5% · EPSS, next 30 days

Weakness

CWE-120 · Classic buffer overflow

Record status

Modified

Affected

• OpenSSL < 3.0.7
• Fedoraproject Fedora 36
• Fedoraproject Fedora 37
• Nodejs node.js < 18.11.0
• Nodejs node.js 18.12.0
• Nodejs node.js 19.0.0

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

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-3786.md and follow it. Check whether this project is affected by CVE-2022-3786. 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