FG-IR-22-419: OpenSSL3 CVE-2022-3602 CVE-2022-3786 vulnerabilities
CVE-2022-3602:
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.
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.
Both the vulnerabilities are 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).
Affected Software
Event History
Frequently Asked Questions
What is the severity of FG-IR-22-419?
The severity of FG-IR-22-419 is high due to the potential for a buffer overrun in X.509 certificate verification.
How do I fix FG-IR-22-419?
To fix FG-IR-22-419, upgrade OpenSSL to version 3.0.8 or higher, which addresses the buffer overrun vulnerability.
What causes the FG-IR-22-419 vulnerability?
FG-IR-22-419 is caused by a buffer overrun that can be triggered during name constraint checking in X.509 certificate verification.
What versions of OpenSSL are affected by FG-IR-22-419?
OpenSSL versions from 3.0.0 to 3.0.7 are affected by FG-IR-22-419.
Is FG-IR-22-419 exploitable in the wild?
Yes, FG-IR-22-419 can be exploited if a malicious certificate is signed by a trusted CA, making it a serious threat.