CVE-2022-4203

A read buffer overrun can be triggered in X.509 certificate verification,<br /> specifically in name constraint checking. Note that this occurs<br /> after certificate chain signature verification and requires either a<br /> CA to have signed the malicious certificate or for the application to<br /> continue certificate verification despite failure to construct a path<br /> to a trusted issuer.<br /> <br /> The read buffer overrun might result in a crash which could lead to<br /> a denial of service attack. In theory it could also result in the disclosure<br /> of private memory contents (such as private keys, or sensitive plaintext)<br /> although we are not aware of any working exploit leading to memory<br /> contents disclosure as of the time of release of this advisory.<br /> <br /> In a TLS client, this can be triggered by connecting to a malicious<br /> server. In a TLS server, this can be triggered if the server requests<br /> client authentication and a malicious client connects.