llamaCVEVulnerability Intelligence
/
OpenSSL

CVE-2024-4741

OpenSSL use-after-free in SSL_free_buffers risks code execution

A remote attacker can corrupt data, crash apps, or possibly run code in apps that call SSL_free_buffers.

Crítica · CVSS alto en tecnología listadaSolo en configuraciones específicasParche disponibleuse-after-free
Descargar PNG JSON
CVSS 3.1
9.8
Crítica
CVSS:3.1/AV:N/AC:L/PR:N/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
Parche5 versiones1.1.1y · 3.0.14 · 3.1.6 · 3.2.2 …
Exposición737 dDesde la divulgación, 13 nov 2024, 5:20 a. m.
Detección719 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCAtender
Priorizar en el próximo ciclo de cambios
Sin explotación conocida, automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV
Verificada
13 nov 24
3 nov 26
6 nov 26
16 nov 26
21 nov 26
13 nov 24
16 may 25
17 nov 25
20 may 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2024-4741 divulgada · CVSS 9.8 (CISA-ADP)
Monitoreo Detectada Ingresó al índice
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 7 nov 2026

Applications that use OpenSSL and directly call the rarely used SSL_free_buffers function can be made to access freed memory, which an attacker could use to corrupt data, crash the application, or potentially run arbitrary code. The attack can be carried out remotely over the network without logging in, but it only works in a non-default setup where the application calls that function while a network record is only partly processed or partly read.

Only affects applications that directly call SSL_free_buffers, on OpenSSL 3.0 to 3.3 and 1.1.1; 1.0.2 and the FIPS modules are not affected. Fixed in 3.3.1, 3.2.2, 3.1.6, 3.0.14 and 1.1.1y.

¿Qué significa?Calling SSL_free_buffers at the wrong moment can leave OpenSSL using memory that was already freed (a use after free). This can corrupt valid data, crash the application, or potentially allow arbitrary code execution.
¿Quién está afectado?OpenSSL 3.3, 3.2, 3.1, 3.0 and 1.1.1 are listed as vulnerable, while 1.0.2 and the FIPS modules are not. Only applications that directly call SSL_free_buffers are affected, and only when a record header has arrived without its full body, or when the application has read only part of a full application data record. The OpenSSL version in use can be checked with the command openssl version, and the application's code or documentation shows whether it calls SSL_free_buffers.
¿Qué hacer?Upgrade to a fixed OpenSSL release: 3.3.1, 3.2.2, 3.1.6, 3.0.14 or 1.1.1y, depending on the branch in use. The advisory text quoted here says 3.3 users should upgrade to 3.3.1 once it is released. No workaround is given.
Descripción original del registro (openssl)

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. 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
Application directly calls SSL_free_buffers“only applications that directly call the SSL_free_buffers function are affected by this issue”
02
Affected OpenSSL versions: 3.3, 3.2, 3.1, 3.0 and 1.1.1 (1.0.2 and the FIPS modules are not affected)“OpenSSL 3.3, 3.2, 3.1, 3.0 and 1.1.1 are vulnerable to this issue.”
03
A record header has been received but the record body has not yet fully arrived when SSL_free_buffers is called“a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived”
04
Or a full application data record was received but the application has read only part of it when SSL_free_buffers is called“the application has only read part of this data”
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:N
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
10.0/ 10Muy alto
Vector 10.0 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
OpenSSL≥ 1.1.1 < 1.1.1y
OpenSSL≥ 3.0.0 < 3.0.14
OpenSSL≥ 3.1.0 < 3.1.6
OpenSSL≥ 3.2.0 < 3.2.2
OpenSSL≥ 3.3.0 < 3.3.1
1.1.1y
1.1.1
3.0.0
3.0.14
3.1.0
3.1.6
3.2.0
3.2.2
3.3.0
3.3.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
OpenSSL
Corregida 1.1.1y, 3.0.14, 3.1.6, 3.2.2, 3.3.1 — —
Versiones corregidas1.1.1y3.0.143.1.63.2.23.3.1
Explotación

Arsenal público

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

Referencias
Fabricantehttps://www.openssl.org/news/secadv/20240528.txt
Fabricantehttps://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4
Parchehttps://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8
Parchehttps://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac
Parchehttps://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177
Parchehttps://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d
Otrahttps://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
Otrahttps://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
Otrahttps://security.netapp.com/advisory/ntap-20240621-0004/

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