CVE-2022-3786

X.509 Email Address Variable Length Buffer Overflow

HIGH
7.5
CVSS Score
Published: November 1, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 05:00 AM UTC
9 products affected across 4 vendorsFedoraOpenSSLNode.js

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 92%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

18.0.0 ≤ v < 18.11.018.12.019.0.0
Affected range stops below 18.11.0, so it looks safe — our inference, not a vendor statement
3.0.0 ≤ v < 3.0.73.0.0
Affected range stops below 3.0.7, so it looks safe — our inference, not a vendor statement
V2022.4 ≤ v < V2023.12022.4
Affected range stops below V2023.1, so it looks safe — our inference, not a vendor statement
V5.2.1 ≤ v < V5.3.05.2.1
Affected range stops below V5.3.0, so it looks safe — our inference, not a vendor statement
V3.2.7 ≤ v < V3.2.83.2.7
Affected range stops below V3.2.8, so it looks safe — our inference, not a vendor statement
V3.2.7 ≤ v < V3.2.83.2.7
Affected range stops below V3.2.8, so it looks safe — our inference, not a vendor statement
V1.80 ≤ v < V2.201.80
Affected range stops below V2.20, so it looks safe — our inference, not a vendor statement
V2.13.0.0 ≤ v < V2.13.0.32.13.0.0
Affected range stops below V2.13.0.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-120

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card