CVE-2022-4203

published 24 Feb 2023 · updated 4 Nov 2025

X.509 Name Constraints Read Buffer Overflow

4.9MediumCVSS 4.9EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in OpenSSL 3.0.8.

A read 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. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. 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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
OpenSSLOpenSSL>=3.0.0 <3.0.83.0.8

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in OpenSSL, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-4203 severity on Zeptric[![CVE-2022-4203](https://zeptric.io/badge/cve/CVE-2022-4203.svg)](https://zeptric.io/cve/CVE-2022-4203)