CVE-2022-3786
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.
- CVSS v3.1
- 7.5 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS v3.1
- 7.5 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS v3.1
- 7.5 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS
- 92.49% chance of exploitation in the next 30 days, 100th percentile
- Published
- 2022-11-01
- Updated
- 2026-04-14
Proof-of-concept exploits (5)
- colmmacc/CVE-2022-3602169★ · 2022-11-01
- cybersecurityworks553/CVE-2022-3602-and-CVE-2022-37864★ · 2022-11-09
- micr0sh0ft/certscare-openssl3-exploit0★ · 2022-11-02
- rbowes-r7/cve-2022-3602-and-cve-2022-3786-openssl-poc17★ · 2022-11-02
- secure-rewind-and-discard/sdrad_utils0★ · 2024-04-14