CVE-2025-9231

{"id": "CVE-2025-9231", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 2.5, "exploitabilityScore": 3.9}]}, "published": "2025-09-30T14:15:41.190", "references": [{"url": "https://github.com/openssl/openssl/commit/567f64386e43683888212226824b6a179885a0fe", "source": "openssl-security@openssl.org"}, {"url": "https://github.com/openssl/openssl/commit/cba616c26ac8e7b37de5e77762e505ba5ca51698", "source": "openssl-security@openssl.org"}, {"url": "https://github.com/openssl/openssl/commit/eed5adc9f969d77c94f213767acbb41ff923b6f4", "source": "openssl-security@openssl.org"}, {"url": "https://github.com/openssl/openssl/commit/fc47a2ec078912b3e914fab5734535e76c4820c2", "source": "openssl-security@openssl.org"}, {"url": "https://openssl-library.org/news/secadv/20250930.txt", "source": "openssl-security@openssl.org"}, {"url": "http://www.openwall.com/lists/oss-security/2025/09/30/5", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2026/05/11/11", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://cert-portal.siemens.com/productcert/html/ssa-032379.html", "source": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e"}, {"url": "https://cert-portal.siemens.com/productcert/html/ssa-089022.html", "source": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e"}, {"url": "https://cert-portal.siemens.com/productcert/html/ssa-253495.html", "source": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "openssl-security@openssl.org", "description": [{"lang": "en", "value": "CWE-385"}]}], "descriptions": [{"lang": "en", "value": "Issue summary: A timing side-channel which could potentially allow remote\nrecovery of the private key exists in the SM2 algorithm implementation on 64 bit\nARM platforms.\n\nImpact summary: A timing side-channel in SM2 signature computations on 64 bit\nARM platforms could allow recovering the private key by an attacker..\n\nWhile remote key recovery over a network was not attempted by the reporter,\ntiming measurements revealed a timing signal which may allow such an attack.\n\nOpenSSL does not directly support certificates with SM2 keys in TLS, and so\nthis CVE is not relevant in most TLS contexts. However, given that it is\npossible to add support for such certificates via a custom provider, coupled\nwith the fact that in such a custom provider context the private key may be\nrecoverable via remote timing measurements, we consider this to be a Moderate\nseverity issue.\n\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\nissue, as SM2 is not an approved algorithm."}, {"lang": "es", "value": "Resumen del problema: Existe un canal lateral de temporizaci\u00f3n que podr\u00eda permitir potencialmente la recuperaci\u00f3n remota de la clave privada en la implementaci\u00f3n del algoritmo SM2 en plataformas ARM de 64 bits.\n\nResumen del impacto: Un canal lateral de temporizaci\u00f3n en los c\u00e1lculos de firma SM2 en plataformas ARM de 64 bits podr\u00eda permitir la recuperaci\u00f3n de la clave privada por un atacante.\n\nAunque el informante no intent\u00f3 la recuperaci\u00f3n remota de la clave a trav\u00e9s de una red, las mediciones de temporizaci\u00f3n revelaron una se\u00f1al de temporizaci\u00f3n que podr\u00eda permitir tal ataque.\n\nOpenSSL no soporta directamente certificados con claves SM2 en TLS, por lo que este CVE no es relevante en la mayor\u00eda de los contextos TLS. Sin embargo, dado que es posible a\u00f1adir soporte para dichos certificados a trav\u00e9s de un proveedor personalizado, junto con el hecho de que en un contexto de proveedor personalizado de este tipo la clave privada podr\u00eda ser recuperable mediante mediciones remotas de temporizaci\u00f3n, consideramos que este es un problema de severidad Moderada.\n\nLos m\u00f3dulos FIPS en 3.5, 3.4, 3.3, 3.2, 3.1 y 3.0 no se ven afectados por este problema, ya que SM2 no es un algoritmo aprobado."}], "lastModified": "2026-06-02T14:16:40.957", "sourceIdentifier": "openssl-security@openssl.org"}