CVE-2022-3786: OpenSSL3 CVE-2022-3602 CVE-2022-3786 vulnerabilities
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.
Other sources
OpenSSL is vulnerable to a denial of service, caused by a stack based buffer overflow during X.509 certificate verification. By using a specially-crafted email address in a certificate, a remote attacker could exploit this vulnerability to cause a TLS client to crash, and results in a denial of service condition.
— IBM
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenSSLto a version that resolves this vulnerability.Fixed in 3.0.7 - Compensating control
Mitigate exposure by ensuring TLS certificate verification does not continue after failure to construct a path to a trusted issuer (the overflow occurs after certificate chain signature verification and requires a CA-signed malicious certificate or an application that continues certificate verification despite failing to build a trust path).
- Compensating control
For TLS client deployments, treat connections to untrusted/malicious servers as high risk because the issue can be triggered by connecting to a malicious server.
- Compensating control
For TLS server deployments with client authentication enabled, treat untrusted client connections as high risk because the issue can be triggered when the server requests client authentication and a malicious client connects.
Event History
Frequently Asked Questions
What is the vulnerability ID of this vulnerability?
The vulnerability ID is CVE-2022-3786.
What is the severity of CVE-2022-3786?
The severity of CVE-2022-3786 is high with a score of 7.5.
How does this vulnerability affect IBM Security Verify Privilege On-Premises?
IBM Security Verify Privilege On-Premises is affected by this vulnerability.
How can a remote attacker exploit this vulnerability?
A remote attacker can exploit this vulnerability by using a specially-crafted email address in a certificate.
What is the recommended action to mitigate this vulnerability?
Apply the necessary security patch or update provided by IBM to fix this vulnerability.