In plain language
What this advisory means
A security flaw in containerd's CRI implementation allows containers restored from untrusted checkpoints to bypass destination security settings and gain elevated privileges. Default Google Kubernetes Engine (GKE) clusters are not affected because they do not include the necessary tool. No immediate action is required for default clusters, but if custom software including the checkpoint restore tool is installed, follow specific security guidance.
Technical explanation
How the issue affects the environment
The vulnerability is in containerd's Container Runtime Interface (CRI) implementation. When a container is restored from an untrusted checkpoint using the CreateContainer API, the process bypasses the destination security context and can execute with elevated privileges. This occurs because the checkpoint restoration does not correctly enforce security context constraints. Google Kubernetes Engine clusters are not vulnerable by default as GKE node images do not include the CRIU (Checkpoint/Restore In Userspace) binary needed to restore from checkpoints.
Operational impact
Why teams should care
Containers restored from untrusted checkpoints could elevate their privileges beyond intended security boundaries, potentially leading to unauthorized access or control over the container host environment. However, since default GKE clusters do not include the checkpoint tool, the risk is limited to environments where custom runtime software with checkpoint restore capabilities is installed.
Immediate action
No immediate action is required for default GKE clusters as they are not vulnerable by default. For nodes with custom runtime software or tools including the CRIU binary, users should refer to the detailed Google Kubernetes Engine security bulletin for recommended mitigation steps.
Affected and fixed releases
Temporary risk reduction
Not specified by the official source. The advisory suggests that avoiding installation of checkpoint restore tools like CRIU on nodes prevents exposure to this issue.
Evidence and validation checklist
- Container restored from an untrusted checkpoint via CreateContainer API bypasses security context.
- GKE clusters are not vulnerable by default.
- GKE node images do not include the criu tool.
- Action is required only if custom software including CRIU is installed.
Authoritative reference
Google Cloud Security Bulletins
QCS detected and normalized this record from the official source. Vendor guidance remains authoritative.