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.
We have discovered 16,092 live websites that are affected by CVE-2022-4203.
Product | ![]() |
Category | Web Server Extensions |
Vulnerable Domains | 16,092 live websites (2.40% of OpenSSL install base) |
Vulnerable Versions |
|
Vulnerable Versions Count | 7 versions ( 17.50% of all versions) |
![]() | 3,623 websites |
![]() | 2,345 websites |
![]() | 1,486 websites |
![]() | 1,317 websites |
![]() | 848 websites |
![]() | 774 websites |
![]() | 688 websites |
![]() | 523 websites |
![]() | 404 websites |
![]() | 397 websites |
.com | 5,684 websites |
.org | 685 websites |
.edu | 652 websites |
.net | 643 websites |
.ca | 638 websites |
.fi | 534 websites |
.jp | 534 websites |
.fr | 489 websites |
.de | 439 websites |
.co.uk | 422 websites |
Domain | Country | Rank | Contacts |
---|---|---|---|
*******.com | ![]() | *,*** | |
***.edu | ![]() | **,*** | |
******.org | ![]() | **,*** | |
********.org | ![]() | **,*** | |
********.com | ![]() | **,*** | |
*******.net | ![]() | **,*** | |
******.****.edu | ![]() | **,*** | |
************************.com | ![]() | **,*** | |
***.com | ![]() | **,*** | |
******.com | ![]() | **,*** |
FAQ