Bypass of seccomp profile enforcement
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/kubernetes Go |
|
|
Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/kubernetes Go |
|
|
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.
From the CVE record · kubernetes
Kubelet does not enforce the seccomp profile for pods configured with a localhost-type seccomp profile and an empty profile field. An affected pod can run unconfined, with seccomp disabled. The input does not specify network access, authentication, or user-interaction requirements.
Operators running Kubernetes with Go package k8s.io/kubernetes versions below 1.24.14, 1.25.0–1.25.9, 1.26.0–1.26.4, or 1.27.0–1.27.1 should check their deployments.