Kubelet vulnerable to bypass of seccomp profile enforcement
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-2431US | medium5.5 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/kubernetes/kubernetesPACKAGE
- https://github.com/kubernetes/kubernetes/issues/118690WEB
- https://github.com/kubernetes/kubernetes/pull/117020WEB
- https://github.com/kubernetes/kubernetes/pull/117116WEB
- https://github.com/kubernetes/kubernetes/pull/117117WEB
- https://github.com/kubernetes/kubernetes/pull/117118WEB
- https://github.com/kubernetes/kubernetes/pull/117147WEB
- https://groups.google.com/g/kubernetes-security-announce/c/QHmx0HOQa10WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan