First published: Tue Nov 01 2022(Updated: )
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.
Credit: openssl-security@openssl.org
Affected Software | Affected Version | How to fix |
---|---|---|
OpenSSL OpenSSL | >=3.0.0<3.0.7 | |
Fedoraproject Fedora | =36 | |
Fedoraproject Fedora | =37 | |
Nodejs Node.js | >=18.0.0<18.11.0 | |
Nodejs Node.js | =18.12.0 | |
Nodejs Node.js | =19.0.0 | |
IBM Security Verify Privilege On-Premises | <=All |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2022-3786.
The severity of CVE-2022-3786 is high with a score of 7.5.
IBM Security Verify Privilege On-Premises is affected by this vulnerability.
A remote attacker can exploit this vulnerability by using a specially-crafted email address in a certificate.
Apply the necessary security patch or update provided by IBM to fix this vulnerability.