As per upstream report: 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 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. OpenSSL versions 3.0.0 to 3.0.6 are vulnerable to this issue. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.7. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
The flaw is Public Now, Lifting Embargoed. https://www.openssl.org/news/secadv/20221101.txt
Created openssl tracking bugs for this issue: Affects: fedora-all [bug 2139151] Created openssl3 tracking bugs for this issue: Affects: epel-all [bug 2139152]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:7288 https://access.redhat.com/errata/RHSA-2022:7288
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:7384 https://access.redhat.com/errata/RHSA-2022:7384