CVE-2026-18540 (LOW): detected in Lambda Docker Images.

Abierto
  • ¿Algo no está bien?
#708 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, docker, node.js
Área
cloud, devops, security

Línea de trabajo

Start by locating the build definitions for the affected Lambda Node.js images: latest, 26-preview, 24, and 22. Check how undici 6.27.0 enters the images, update it to a listed fixed version, then rebuild and scan the images to confirm the vulnerable version is absent.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

CVE Details

CVE ID Severity Affected Package Installed Version Fixed Version Date Published Date of Scan
CVE-2026-18540 LOW undici 6.27.0 6.28.1, 7.29.1, 8.10.2 2026-09-04T18:17:50.02Z 2026-09-30T10:18:20.696138078Z

Affected Docker Images

Image Name SHA
public.ecr.aws/lambda/nodejs:latest public.ecr.aws/lambda/nodejs@sha256:523ce8499e16c3bff599c94691e1c6a1405aac415c13b95b98dbb9dddd052b77
public.ecr.aws/lambda/nodejs:26-preview public.ecr.aws/lambda/nodejs@sha256:f5118e838e4efe4462b87cb77b1b255170952560a5766ad9c0d3f30016c57800
public.ecr.aws/lambda/nodejs:24 public.ecr.aws/lambda/nodejs@sha256:523ce8499e16c3bff599c94691e1c6a1405aac415c13b95b98dbb9dddd052b77
public.ecr.aws/lambda/nodejs:22 public.ecr.aws/lambda/nodejs@sha256:282bd7028e6d1f365a3a174751634c7a84e12ef8a466cdcf786c3f4d744e743a

Description

undici's retry interceptor can append the body of a ranged retry response to bytes already delivered from an earlier partial response while still presenting the original response's status and headers. This happens when an upstream server delivers part of a body without a trustworthy resume checkpoint, for example a non-success response whose headers were already sent or a partial-content response with an unusable content range, then closes the connection and answers the resumed range request with more bytes. As a result the response body can be longer than the Content-Length that the application observes. An application that relays such a response to a downstream HTTP/1.1 peer without normalizing the framing can emit a body that exceeds the forwarded Content-Length, and the excess bytes can be interpreted as the start of a following response, which enables downstream response splitting or desynchronization. Exploitation requires an attacker-controlled upstream server and an application that forwards the response through a framing-sensitive path. This affects undici versions before 6.28.1, from 7.0.0 up to 7.29.1, and from 8.0.0 up to 8.10.2. Users should upgrade to undici 6.28.1, 7.29.1, or 8.10.2.

Remediation Steps
  • Update the affected package undici from version 6.27.0 to 6.28.1, 7.29.1, 8.10.2.
About this issue
  • This issue may not contain all the information about the CVE nor the images it affects.
  • This issue will not be updated with new information and the list of affected images may have changed since the creation of this issue.
  • For more, visit Lambda Watchdog.
  • This issue was created automatically by Lambda Watchdog.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
775
Forks
117
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aws/aws-lambda-base-images

Todos los issues de aws/aws-lambda-base-images

Issues similares

Más issues de Cloud

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.