github.com/containerd/containerd
Affected
- introduced
0, fixed1.7.29(semver)
Fixed versions
1.7.29
Fix
- Fixed version
1.7.29go get github.com/containerd/[email protected]
Advisory
Also known as: CVE-2024-25621, GO-2025-4100
containerd affected by a local privilege escalation via wide permissions on CRI directory
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/run/containerd/io.containerd.grpc.v1.cri was created with 0o755, while it should be created with 0o700/run/containerd/io.containerd.sandbox.controller.v1.shim was created with 0o711, while it should be created with 0o700The 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:
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:
High Basis: The source's own band: HIGH
0, fixed 1.7.29 (semver)1.7.29
1.7.29go get github.com/containerd/[email protected]0, fixed 2.0.7 (semver)2.0.7
2.0.7go get github.com/containerd/containerd/[email protected]2.1.0-beta.0, fixed 2.1.5 (semver)2.1.5
2.1.5go get github.com/containerd/containerd/[email protected]2.2.0-beta.0, fixed 2.2.0 (semver)2.2.0
2.2.0go get github.com/containerd/containerd/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0