OpenSSL X.509 Email Address 4-byte Buffer Overflow
CVE-2022-3602 is a stack-based buffer overflow in OpenSSL 3.0.0 through 3.0.6 during X.509 certificate verification, specifically in name constraint checking involving punycode-decoded email address handling. The flaw was introduced in OpenSSL 3.0.0 in the punycode decoding functionality used for processing email address name constraints in X.509 certificates. A malicious certificate can trigger an overflow of four attacker-controlled bytes on the stack after certificate chain signature verification. In practice, the vulnerable path is reachable when an OpenSSL 3.0 application verifies X.509 certificates from untrusted sources, including TLS clients connecting to malicious servers and TLS servers that request client authentication from malicious clients. OpenSSL 1.0.2, 1.1.1, and earlier branches are not affected. The issue was fixed in OpenSSL 3.0.7.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).
This repository contains a proof-of-concept (PoC) exploit for CVE-2022-3602, a buffer overflow vulnerability in OpenSSL versions 3.0 to below 3.0.7. The main file, 'CVE-2022-3602.c', is a C program that connects to a specified IP and port (typically where a vulnerable OpenSSL service is running) and sends a crafted payload designed to trigger a buffer overflow, potentially causing a Denial of Service (DoS). The payload is generated using a hardcoded array and a simple RC4-like algorithm. The README provides compilation and usage instructions, demonstrating how to target a local or remote service. No detection or scanning functionality is present; the code is solely for exploitation. The attack vector is network-based, requiring the attacker to connect to the target service. The repository is structured simply, with one exploit source file and a README.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenSSL vulnerability associated in the content with punycode/email address handling and overflows in X.509 certificate email address processing.
An OpenSSL vulnerability involving punycode in X.509 certificates, specifically noted as appearing within the leaf certificate and relevant to certificate inspection/detection.
A prior OpenSSL vulnerability referenced for historical comparison as the last OpenSSL RCE-designated issue before the newly disclosed high-severity flaw.
A buffer overflow vulnerability in OpenSSL punycode decoding functions.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.