Advisory

GHSA-pwhc-rpq9-4c8w

Also known as: CVE-2024-25621, GO-2025-4100

Summary

containerd affected by a local privilege escalation via wide permissions on CRI directory

Details

Impact

An overly broad default permission vulnerability was found in containerd.

  • /var/lib/containerd was created with the permission bits 0o711, while it should be created with 0o700
  • Allowed local users on the host to potentially access the metadata store and the content store
  • /run/containerd/io.containerd.grpc.v1.cri was created with 0o755, while it should be created with 0o700
  • Allowed local users on the host to potentially access the contents of Kubernetes local volumes. The contents of volumes might include setuid binaries, which could allow a local user on the host to elevate privileges on the host.
  • /run/containerd/io.containerd.sandbox.controller.v1.shim was created with 0o711, while it should be created with 0o700

The directory paths may differ depending on the daemon configuration.
When the temp directory path is specified in the daemon configuration, that directory was also created with 0o711, while it should be created with 0o700.

Patches

This bug has been fixed in the following containerd versions:

  • 2.2.0
  • 2.1.5
  • 2.0.7
  • 1.7.29

Users should update to these versions to resolve the issue.
These updates automatically change the permissions of the existing directories.

> [!NOTE]
>
> /run/containerd and /run/containerd/io.containerd.runtime.v2.task are still created with 0o711.
> This is an expected behavior for supporting userns-remapped containers.

Workarounds

The system administrator on the host can manually chmod the directories to not
have group or world accessible permisisons:

chmod 700 /var/lib/containerd
chmod 700 /run/containerd/io.containerd.grpc.v1.cri
chmod 700 /run/containerd/io.containerd.sandbox.controller.v1.shim

An alternative mitigation would be to run containerd in rootless mode.

Credits

The containerd project would like to thank David Leadbeater for responsibly disclosing this issue in accordance with the containerd security policy.

For more information

If you have any questions or comments about this advisory:

To report a security issue in containerd:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-11-06 15:12 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 0, fixed 1.7.29 (semver)

Fixed versions

1.7.29

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 0, fixed 2.0.7 (semver)

Fixed versions

2.0.7

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 2.1.0-beta.0, fixed 2.1.5 (semver)

Fixed versions

2.1.5

Fix

github.com/containerd/containerd/v2

Go · All systems

Affected

  • introduced 2.2.0-beta.0, fixed 2.2.0 (semver)

Fixed versions

2.2.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences