CVE-2024-9143

{"id": "CVE-2024-9143", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.8}]}, "published": "2024-10-16T17:15:18.130", "references": [{"url": "https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712", "source": "[email protected]"}, {"url": "https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700", "source": "[email protected]"}, {"url": "https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4", "source": "[email protected]"}, {"url": "https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154", "source": "[email protected]"}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a", "source": "[email protected]"}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41", "source": "[email protected]"}, {"url": "https://openssl-library.org/news/secadv/20241016.txt", "source": "[email protected]"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/16/1", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/23/1", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/24/1", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.netapp.com/advisory/ntap-20241101-0001/", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-125"}, {"lang": "en", "value": "CWE-787"}]}], "descriptions": [{"lang": "en", "value": "Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted\nexplicit values for the field polynomial can lead to out-of-bounds memory reads\nor writes.\n\nImpact summary: Out of bound memory writes can lead to an application crash or\neven a possibility of a remote code execution, however, in all the protocols\ninvolving Elliptic Curve Cryptography that we're aware of, either only \"named\ncurves\" are supported, or, if explicit curve parameters are supported, they\nspecify an X9.62 encoding of binary (GF(2^m)) curves that can't represent\nproblematic input values. Thus the likelihood of existence of a vulnerable\napplication is low.\n\nIn particular, the X9.62 encoding is used for ECC keys in X.509 certificates,\nso problematic inputs cannot occur in the context of processing X.509\ncertificates. Any problematic use-cases would have to be using an \"exotic\"\ncurve encoding.\n\nThe affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),\nand various supporting BN_GF2m_*() functions.\n\nApplications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,\nthat make it possible to represent invalid field polynomials with a zero\nconstant term, via the above or similar APIs, may terminate abruptly as a\nresult of reading or writing outside of array bounds. Remote code execution\ncannot easily be ruled out.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}, {"lang": "es", "value": "Resumen del problema: el uso de las API de curva el\u00edptica GF(2^m) de bajo nivel con valores expl\u00edcitos no confiables para el campo polinomial puede generar lecturas o escrituras de memoria fuera de los l\u00edmites. Resumen del impacto: las escrituras de memoria fuera de los l\u00edmites pueden generar un bloqueo de la aplicaci\u00f3n o incluso la posibilidad de una ejecuci\u00f3n de c\u00f3digo remoto; sin embargo, en todos los protocolos que involucran criptograf\u00eda de curva el\u00edptica que conocemos, solo se admiten \"curvas con nombre\" o, si se admiten par\u00e1metros de curva expl\u00edcitos, especifican una codificaci\u00f3n X9.62 de curvas binarias (GF(2^m)) que no pueden representar valores de entrada problem\u00e1ticos. Por lo tanto, la probabilidad de existencia de una aplicaci\u00f3n vulnerable es baja. En particular, la codificaci\u00f3n X9.62 se utiliza para claves ECC en certificados X.509, por lo que no pueden ocurrir entradas problem\u00e1ticas en el contexto del procesamiento de certificados X.509. Cualquier caso de uso problem\u00e1tico tendr\u00eda que utilizar una codificaci\u00f3n de curva \"ex\u00f3tica\". Las API afectadas incluyen: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params() y varias funciones de soporte BN_GF2m_*(). Las aplicaciones que trabajan con par\u00e1metros de curva binarios expl\u00edcitos \"ex\u00f3ticos\" (GF(2^m)), que permiten representar polinomios de campo no v\u00e1lidos con un t\u00e9rmino constante cero, a trav\u00e9s de las API anteriores o similares, pueden terminar abruptamente como resultado de la lectura o escritura fuera de los l\u00edmites de la matriz. La ejecuci\u00f3n remota de c\u00f3digo no se puede descartar f\u00e1cilmente. Los m\u00f3dulos FIPS en 3.3, 3.2, 3.1 y 3.0 no se ven afectados por este problema."}], "lastModified": "2025-11-03T23:17:33.460", "sourceIdentifier": "[email protected]"}