CVE-2022-3786

Published: 1 November 2022

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.

Notes

3.x only
While developing the fix for CVE-2022-3602, a second buffer
overflow was discovered and this additional CVE was issued.
The updated packages that fix this issue ommited the CVE number
from the changelog as it was assigned at a later date.

Status

Severity score breakdown

References

• https://www.openssl.org/news/secadv/20221101.txt
• https://ubuntu.com/security/notices/USN-5710-1
• https://www.cve.org/CVERecord?id=CVE-2022-3786
• NVD
• Launchpad
• Debian