llamaCVEVulnerability Intelligence
/
OpenSSL

CVE-2024-9143

OpenSSL out-of-bounds read in GF(2^m) curve parameters

An attacker supplying crafted explicit binary curve parameters can crash an application or possibly run code remotely.

Texto original en inglés · Ver en español

Crítica · EPSS ≥ 10 %Solo en configuraciones específicasParche disponibleout-of-bounds read
Descargar PNG JSON
CVSS 3.1
8.8
Alta
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Fuente: CISA-ADP
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche6 versiones1.0.2zl · 1.1.1zb · 3.0.16 · 3.1.8 …
Exposición766 dDesde la divulgación, 16 oct 2024, 12:09 p. m.
EPSS ≥ 10 %10 nov 2026Fecha en que la probabilidad de explotación superó el umbral
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Yo la vigilo, tú la programas. ¿Trato?Huele a "ya lo veré". No la dejes así.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Umbral EPSS
Remediación
Monitoreo
Detectada
Fuente: OSV
Verificada
16 oct 24
22 oct 26
24 oct 26
6 nov 26
10 nov 26
16 nov 26
21 nov 26
16 oct 24
26 abr 25
3 nov 25
14 may 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2024-9143 divulgada · CVSS 8.8 (CISA-ADP)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Explotación Umbral EPSS La probabilidad de explotación supera el 10 %
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 10 nov 2026

The OpenSSL elliptic curve APIs for binary (GF(2^m)) curves can be made to read or write outside array bounds when given untrusted, explicitly specified field polynomials. An attacker who can reach such an application over the network, with low-privilege login and no user action, could crash it or potentially execute code, though exploitation is considered unlikely because standard protocols and X.509 certificates cannot express the problematic values.

Only applications calling OpenSSL's low-level GF(2^m) elliptic curve APIs with untrusted explicit curve parameters are affected. Fixed in 3.3.3, 3.2.4, 3.1.8, 3.0.16, 1.1.1zb and 1.0.2zl.

¿Qué significa?Explicit binary (GF(2^m)) elliptic curve parameters with an invalid field polynomial, specifically one with a zero constant term, can make OpenSSL read or write memory outside its allocated bounds. This can crash the application, and remote code execution cannot easily be ruled out.
¿Quién está afectado?Affected versions are OpenSSL 3.3.0 to before 3.3.3, 3.2.0 to before 3.2.4, 3.1.0 to before 3.1.8, 3.0.0 to before 3.0.16, 1.1.1 to before 1.1.1zb, and 1.0.2 to before 1.0.2zl. Check the installed version with the command 'openssl version'. The issue requires an application that uses the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial.
¿Qué hacer?OpenSSL 3.3 users should upgrade to 3.3.3. Users of other branches should upgrade to the fixed release for their branch: 3.2.4, 3.1.8, 3.0.16, 1.1.1zb or 1.0.2zl.
Descripción original del registro (openssl)

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial“Use of the low-level GF(2^m) elliptic curve APIs with untrusted”
02
Explicit binary (GF(2^m)) curve parameters that represent invalid field polynomials with a zero constant term ("exotic" encodings)“Applications working with "exotic" explicit binary (GF(2^m)) curve parameters,”
¿Quién debe revisar?Teams shipping OpenSSL 3.3, 3.2, 3.1, 3.0, 1.1.1 or 1.0.2 that accept explicit binary (GF(2^m)) EC curve parameters from untrusted input.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CISA-ADP
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
8.3/ 10Alto
Vector 8.3 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
OpenSSL≥ 1.0.2 < 1.0.2zl
OpenSSL≥ 1.1.1 < 1.1.1zb
OpenSSL≥ 3.0.0 < 3.0.16
OpenSSL≥ 3.1.0 < 3.1.8
OpenSSL≥ 3.2.0 < 3.2.4
OpenSSL≥ 3.3.0 < 3.3.3
1.0.2zl
1.0.2
1.1.1zb
1.1.1
3.0.0
3.0.16
3.1.0
3.1.8
3.2.0
3.2.4
3.3.0
3.3.3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
OpenSSL
Corregida 1.0.2zl, 1.1.1zb, 3.0.16, 3.1.8, 3.2.4, 3.3.3 — —
Versiones corregidas1.0.2zl1.1.1zb3.0.163.1.83.2.43.3.3
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://openssl-library.org/news/secadv/20241016.txt
Fabricantehttps://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
Fabricantehttps://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
Parchehttps://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
Parchehttps://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
Parchehttps://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
Parchehttps://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
Análisishttp://www.openwall.com/lists/oss-security/2024/10/16/1
Análisishttp://www.openwall.com/lists/oss-security/2024/10/23/1
Análisishttp://www.openwall.com/lists/oss-security/2024/10/24/1
Otrahttps://security.netapp.com/advisory/ntap-20241101-0001/
Otrahttps://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
Ver 5 referencias más
Otrahttps://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
Otrahttps://cert-portal.siemens.com/productcert/html/ssa-398330.html
Otrahttps://cert-portal.siemens.com/productcert/html/ssa-265688.html
Otrahttps://cert-portal.siemens.com/productcert/html/ssa-769027.html
Otrahttps://cert-portal.siemens.com/productcert/html/ssa-277137.html

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.