CVE-2022-4203

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.

CVSS v3 4.9 MEDIUM

4.9^/10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.2 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc	Mailing List Patch
https://security.gentoo.org/glsa/202402-08
https://www.openssl.org/news/secadv/20230207.txt	Vendor Advisory
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc	Mailing List Patch
https://security.gentoo.org/glsa/202402-08
https://www.openssl.org/news/secadv/20230207.txt	Vendor Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*

History

21 Nov 2024, 07:34

Type	Values Removed	Values Added
Summary		(es) Un desbordamiento del búfer de lectura puede activarse en la verificación de certificados X.509, específicamente en la verificación de restricciones de nombre. Tenga en cuenta que esto ocurre después de la verificación de la firma de la cadena de certificados y requiere que una CA haya firmado el certificado malicioso o que la aplicación continúe con la verificación del certificado a pesar de no poder construir una ruta a un emisor de confianza. El desbordamiento del búfer de lectura puede provocar un bloqueo que podría conducir a un ataque de denegación de servicio. En teoría, también podría provocar la divulgación de contenidos de memoria privada (como claves privadas o texto plano confidencial), aunque no conocemos ningún exploit en funcionamiento que conduzca a la divulgación de contenidos de memoria al momento de la publicación de este aviso. En un cliente TLS, esto puede activarse al conectarse a un servidor malicioso. En un servidor TLS, esto puede activarse si el servidor solicita la autenticación del cliente y un cliente malicioso se conecta.
References	~~() https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc - Mailing List, Patch~~	() https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc - Mailing List, Patch
References	~~() https://security.gentoo.org/glsa/202402-08 -~~	() https://security.gentoo.org/glsa/202402-08 -
References	~~() https://www.openssl.org/news/secadv/20230207.txt - Vendor Advisory~~	() https://www.openssl.org/news/secadv/20230207.txt - Vendor Advisory

04 Feb 2024, 09:15

Type	Values Removed	Values Added
References		() https://security.gentoo.org/glsa/202402-08 -

07 Nov 2023, 03:57

Type	Values Removed	Values Added
Summary	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.	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.

Information

Published : 2023-02-24 15:15

Updated : 2024-11-21 07:34

NVD link : CVE-2022-4203

Mitre link : CVE-2022-4203

CVE.ORG link : CVE-2022-4203

JSON object : View

Products Affected

openssl

openssl

CWE

CWE-125

Out-of-bounds Read

4.9 /10