llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/containerd/containerd

GHSA-7WW5-4WQC-M92C

containerd allows RAPL to be accessible to a container

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versionesPrimer parche a -11 d de la divulgación
Exposición1.067 dDesde la divulgación, 19 dic 2023, 4:17 p. m.
Detección1.063 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.6.26 +1
Monitoreo
Detectada
8 dic 23
19 dic 23
10 sept 26
17 nov 26
20 nov 26
8 dic 23
3 sept 24
30 may 25
24 feb 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche v1.6.26 github.com/containerd/containerd · -11 d desde divulgación
Remediación Parche v1.7.11 github.com/containerd/containerd · -11 d desde divulgación
Divulgación Publicada GHSA-7WW5-4WQC-M92C divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

/sys/devices/virtual/powercap accessible by default to containers

Intel's RAPL (Running Average Power Limit) feature, introduced by the Sandy Bridge microarchitecture, provides software insights into hardware energy consumption. To facilitate this, Intel introduced the powercap framework in Linux kernel 3.13, which reads values via relevant MSRs (model specific registers) and provides unprivileged userspace access via `sysfs`. As RAPL is an interface to access a hardware feature, it is only available when running on bare metal with the module compiled into the kernel.

By 2019, it was realized that in some cases unprivileged access to RAPL readings could be exploited as a power-based side-channel against security features including AES-NI (potentially inside a SGX enclave) and KASLR (kernel address space layout randomization). Also known as the PLATYPUS attack https://platypusattack.com/, Intel assigned CVE-2020-8694 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8694 and CVE-2020-8695 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8695, and AMD assigned CVE-2020-12912 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12912.

Several mitigations were applied; Intel reduced the sampling resolution via a microcode update, and the Linux kernel prevents access by non-root users https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=949dd0104c496fa7c14991a23c03c62e44637e71 since 5.10. However, this kernel-based mitigation does not apply to many container-based scenarios:
* Unless using user namespaces, root inside a container has the same level of privilege as root outside the container, but with a slightly more narrow view of the system
* `sysfs` is mounted inside containers read-only; however only read access is needed to carry out this attack on an unpatched CPU

While this is not a direct vulnerability in container runtimes, defense in depth and safe defaults are valuable and preferred, especially as this poses a risk to multi-tenant container environments. This is provided by masking `/sys/devices/virtual/powercap` in the default mount configuration, and adding an additional set of rules to deny it in the default AppArmor profile.

While `sysfs` is not the only way to read from the RAPL subsystem, other ways of accessing it require additional capabilities such as `CAP_SYS_RAWIO` which is not available to containers by default, or `perf` paranoia level less than 1, which is a non-default kernel tunable.

References

  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8694
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8695
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12912
  • https://platypusattack.com/
  • https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=949dd0104c496fa7c14991a23c03c62e44637e71
  • https://web.eece.maine.edu/~vweaver/projects/rapl/

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
github.com/containerd/containerd< 1.6.26
github.com/containerd/containerd≥ 1.7.0 < 1.7.11
1.6.26
1.7.0
1.7.11
v1.7.36
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/containerd/containerd
Corregida v1.6.26, v1.7.11 -11 d · -11 d v1.7.36 no afectada
Versiones corregidas1.6.26v1.6.261.7.11v1.7.11
Explotación

Arsenal público

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

Referencias
Otrahttps://github.com/containerd/containerd/security/advisories/GHSA-7ww5-4wqc-m92c
Otrahttps://github.com/containerd/containerd/commit/67d356cb3095f3e8f8ad7d36f9a733fea1e7e28c
Otrahttps://github.com/containerd/containerd/commit/746b910f05855c8bfdb4415a1c0f958b234910e5
Otrahttps://github.com/containerd/containerd

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