CVE-2022-3602
X.509 Email Address 4-byte Buffer Overflow
- Published
- Nov 1, 2022
- Updated
- Apr 14, 2026
- Assigning CNA
- openssl
- Evidence observed
- Aug 8, 2026
Primary CVSS
nvd · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh · next 30 days
- Percentile
- 99.8%
- Model date
- Nov 6, 2026
EPSS is a statistical estimate, not a certainty or a measure of impact. Combine it with CVSS, KEV status, exposure and your environment.
Summary
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 the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution. Many platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler. Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible. 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. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6).
Sources
- CVE-2022-3602Research
Technical deep-dive and anti-POC for CVE-2022-3602, a punycode buffer overflow in OpenSSL 3.0.x, with reproduction scripts, stack analysis, and compiler mitigation evaluation.
- CVE-2022-3602Detection
Zeek package detecting CVE-2022-3602 exploitation attempts and vulnerable OpenSSL servers via HTTP Server header and TLS punycode anomalies, generating actionable notices for incident response.
Python-based scanner that detects OpenSSL 3.0.0-3.0.6 servers vulnerable to CVE-2022-3602 and CVE-2022-3786 by checking client authentication requirements on single or multiple targets.
Proof-of-concept exploit for CVE-2022-3602, a buffer overflow denial-of-service vulnerability in OpenSSL 3.0 before 3.0.7. Includes C source code and compilation instructions.
- spookyssl-pcapsDetection
PCAPs and Suricata signatures for detecting OpenSSL CVE-2022-3602 exploitation attempts, including malicious client/server traffic and legitimate punycode certificate examples.
- OpenSSL-2022Informational
Operational information regarding CVE-2022-3602 and CVE-2022-3786, two vulnerabilities in OpenSSL 3
Proof-of-concept exploit for OpenSSL buffer overflow vulnerabilities CVE-2022-3602 and CVE-2022-3786, demonstrating remote code execution via crafted X.509 certificates.
cve-2022-3602 poc
- jfrog-openssl-toolsScanner
Python utilities to check whether a TLS server requires client certificates and to scan local ELF binaries for vulnerable OpenSSL 3.x code linked to CVE-2022-3602 and CVE-2022-3786.
Proof of concept code for Datadog Security Labs referenced exploits.
Responsible use
Use vulnerability information only on systems you own or are authorized to test. Kitploit links to public research metadata and does not store exploit code or malicious payloads.