First published: Fri Jun 16 2023(Updated: )
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. References: <a href="https://groups.google.com/g/kubernetes-security-announce/c/QHmx0HOQa10">https://groups.google.com/g/kubernetes-security-announce/c/QHmx0HOQa10</a> <a href="https://github.com/kubernetes/kubernetes/issues/118690">https://github.com/kubernetes/kubernetes/issues/118690</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Kubernetes Kubelet |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2215555 is considered critical due to the potential for pods to bypass seccomp profile enforcement.
To fix REDHAT-BUG-2215555, update your Kubernetes Kubelet to a patched version that properly enforces seccomp profiles.
All versions of Kubernetes Kubelet that allow pods to specify an empty seccomp profile field are affected by REDHAT-BUG-2215555.
REDHAT-BUG-2215555 allows attackers to run pods in an unconfined security context, potentially exposing the host to security risks.
A temporary workaround for REDHAT-BUG-2215555 is to avoid using empty seccomp profile fields in your pod specifications.