| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| github.com/containerd/containerd | 全バージョン | |
| github.com/containerd/containerd/v2 | ≥ 2.1.0, < 2.1.9≥ 2.2.0, < 2.2.5≥ 2.3.0, < 2.3.2 | 2.1.92.2.52.3.2 |
| containerd | ≥ 2.1.0, < 2.1.9≥ 2.2.0, < 2.2.5≥ 2.3.0, < 2.3.2 | 2.1.92.2.52.3.2 |
containerd's CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected.
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue. Recreating existing containers restored from untrusted checkpoints may be necessary to remove smuggled configuration.
Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images. If Container Device Interface (CDI) capabilities are not utilized on the node, removing or temporarily relocating host CDI specifications from the default directories (/etc/cdi and /var/run/cdi) will eliminate the reachability of this vulnerability.
The containerd project would like to thank Robert Prast (@robertprast) for responsibly disclosing this issue in accordance with the containerd security policy.
If you have any questions or comments about this advisory:
To report a security issue in containerd:
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン