← Übersicht containerd

containerd started with non-empty inheritable Linux process capabilities

GHSA-c9cp-9c75-9v8c · GO-2024-2846

Ohne Bewertung Unbekannt Fix verfügbar

Veröffentlicht
15.05.2024 00:04
Zuletzt geändert
08.07.2024
EPSS (30 Tage)
unbekannt
CVSS-Vektor
keiner

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact A bug was found in containerd where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted. This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. ### Patches This bug has been fixed in containerd 1.5.11 and 1.6.2. Users should update to these versions as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes containerd behavior such that containers are started with a more typical Linux environment. Refer to `capabilities(7)` for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox. ### Workarounds The entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting. ### For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/containerd/containerd/issues/new) * Email us at [security@containerd.io](mailto:security@containerd.io) if you think you’ve found a security bug

Betroffene Pakete im beobachteten Stack

Gogithub.com/containerd/containerd1.5.11GHSA-c9cp-9c75-9v8c
Gogithub.com/containerd/containerd1.6.0 → 1.6.2GHSA-c9cp-9c75-9v8c
Gogithub.com/containerd/containerd1.5.11, 1.6.0 → 1.6.2GO-2024-2846

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Unbekannt) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.