llamaCVEVulnerability Intelligence
/
containerd

CVE-2020-15157

containerd can be coerced into leaking credentials during image pull

Parche disponibleexposed credentials
Descargar PNG JSON
CVSS 3.1
6.1
Media
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N Fuente: CNA
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -1 d de la divulgación
Exposición2.224 dDesde la divulgación, 16 oct 2020, 11:45 a. m.
Detección2.222 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche v1.2.14
Monitoreo
Detectada
15 oct 20
16 oct 20
4 ago 24
17 nov 26
19 nov 26
15 oct 20
25 abr 22
2 nov 23
12 may 25
19 nov 26
FechaFaseEventoDetalle
Remediación Parche v1.2.14 github.com/containerd/containerd · -1 d desde divulgación
Divulgación Publicada CVE-2020-15157 divulgada · CVSS 6.1 (CNA)
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen

In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
containerd · github.com/containerd/containerd< 1.2.14
1.2.14
v1.7.36
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/containerd/containerd
Corregida v1.2.14 -1 d v1.7.36 no afectada
Versiones corregidas1.2.14v1.2.14
Explotación

Arsenal público

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

Referencias
Advisoryhttps://usn.ubuntu.com/4589-1/
Advisoryhttps://usn.ubuntu.com/4589-2/
Advisoryhttps://www.debian.org/security/2021/dsa-4865
Fabricantehttps://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c
Otrahttps://github.com/containerd/containerd/releases/tag/v1.2.14

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