OpenSSL · OpenSSL
The flaw is a buffer overrun in OpenSSL's X.509 certificate verification, specifically in name constraint checking, which lets an attacker overflow four attacker-controlled bytes on the stack using a crafted email address. An attacker can trigger it remotely by connecting a TLS client to a malicious server, or by having a malicious client connect to a TLS server that requests client authentication, and exploitation requires that a CA signed the malicious certificate or that the application continues verification after failing to build a path to a trusted issuer.
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).
Public exploit code (PoC-in-GitHub) was available 4 days before disclosure.
7 fixes in openssl-src over 8 months. The latest fix listed for openssl-src is 300.0.12.
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
1 package in 1 ecosystem. Main package: openssl-src.
Upgrade to 300.0.12 or later
Fixes this CVE and 3 other known vulnerabilities in this package (CVE-2022-0778, CVE-2022-3786, +1).
cargo update -p openssl-src --precise 300.0.12First fixed in 300.0.11 for CVE-2022-3602.
| If you run | Upgrade to |
|---|---|
| 300.0.0 up to 300.0.11 | 300.0.12first fix for this CVE: 300.0.11 |
“Up to” means the second version is the fix and is not affected.
Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.