Vulnerabilities · 2022 · Openssl
CVE-2022-3786
Openssl vulnerability
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.
Affected products
Openssl, Fedora, Node.js. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Openssl runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c42165b5706e42f67ef8ef4c351a9a4c5d216 · Patch
- www.openssl.org/news/secadv/20221101.txt · Vendor Advisory
- www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00789.html
- www.kb.cert.org/vuls/id/794340
- cert-portal.siemens.com/productcert/html/ssa-408105.html
- nvd.nist.gov/vuln/detail/CVE-2022-3786
- cve.org/CVERecord?id=CVE-2022-3786
More vulnerabilities in Openssl products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.