CVE-2024-12797

{"id": "CVE-2024-12797", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 2.8}]}, "published": "2025-02-11T16:15:38.827", "references": [{"url": "https://github.com/openssl/openssl/commit/738d4f9fdeaad57660dcba50a619fafced3fd5e9", "source": "openssl-security@openssl.org"}, {"url": "https://github.com/openssl/openssl/commit/798779d43494549b611233f92652f0da5328fbe7", "source": "openssl-security@openssl.org"}, {"url": "https://github.com/openssl/openssl/commit/87ebd203feffcf92ad5889df92f90bb0ee10a699", "source": "openssl-security@openssl.org"}, {"url": "https://openssl-library.org/news/secadv/20250211.txt", "source": "openssl-security@openssl.org"}, {"url": "http://www.openwall.com/lists/oss-security/2025/02/11/3", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2025/02/11/4", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.netapp.com/advisory/ntap-20250214-0001/", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "openssl-security@openssl.org", "description": [{"lang": "en", "value": "CWE-392"}]}], "descriptions": [{"lang": "en", "value": "Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a\nserver may fail to notice that the server was not authenticated, because\nhandshakes don't abort as expected when the SSL_VERIFY_PEER verification mode\nis set.\n\nImpact summary: TLS and DTLS connections using raw public keys may be\nvulnerable to man-in-middle attacks when server authentication failure is not\ndetected by clients.\n\nRPKs are disabled by default in both TLS clients and TLS servers. The issue\nonly arises when TLS clients explicitly enable RPK use by the server, and the\nserver, likewise, enables sending of an RPK instead of an X.509 certificate\nchain. The affected clients are those that then rely on the handshake to\nfail when the server's RPK fails to match one of the expected public keys,\nby setting the verification mode to SSL_VERIFY_PEER.\n\nClients that enable server-side raw public keys can still find out that raw\npublic key verification failed by calling SSL_get_verify_result(), and those\nthat do, and take appropriate action, are not affected. This issue was\nintroduced in the initial implementation of RPK support in OpenSSL 3.2.\n\nThe FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}, {"lang": "es", "value": "Resumen del problema: los clientes que utilizan claves p\u00fablicas sin procesar (RPK) RFC7250 para autenticar un servidor pueden no darse cuenta de que el servidor no se ha autenticado, porque los protocolos de enlace no se cancelan como se espera cuando se establece el modo de verificaci\u00f3n SSL_VERIFY_PEER. Resumen del impacto: las conexiones TLS y DTLS que utilizan claves p\u00fablicas sin procesar pueden ser vulnerables a ataques de intermediarios cuando los clientes no detectan un error de autenticaci\u00f3n del servidor. Las RPK est\u00e1n deshabilitadas de forma predeterminada tanto en los clientes TLS como en los servidores TLS. El problema solo surge cuando los clientes TLS habilitan expl\u00edcitamente el uso de RPK por parte del servidor y el servidor, a su vez, habilita el env\u00edo de una RPK en lugar de una cadena de certificados X.509. Los clientes afectados son aquellos que dependen de que el protocolo de enlace falle cuando la RPK del servidor no coincide con una de las claves p\u00fablicas esperadas, al establecer el modo de verificaci\u00f3n en SSL_VERIFY_PEER. Los clientes que habilitan claves p\u00fablicas sin procesar del lado del servidor a\u00fan pueden descubrir que la verificaci\u00f3n de clave p\u00fablica sin procesar fall\u00f3 al llamar a SSL_get_verify_result(), y aquellos que lo hacen y toman las medidas adecuadas no se ven afectados. Este problema se introdujo en la implementaci\u00f3n inicial de la compatibilidad con RPK en OpenSSL 3.2. Los m\u00f3dulos FIPS en 3.4, 3.3, 3.2, 3.1 y 3.0 no se ven afectados por este problema."}], "lastModified": "2025-02-18T14:15:27.107", "sourceIdentifier": "openssl-security@openssl.org"}