CVE-2019-11245GHSA-R76G-G87F-VW8FGO-2024-2780
kubelet-started container uid changes to root after first restart or if image is already pulled to the node
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.14.3, 1.13.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit runAsUser attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified mustRunAsNonRoot: true, the kubelet will refuse to start the container as root. If the pod did not specify mustRunAsNonRoot: true, the kubelet will run the container as uid 0.
Timeline
- CVE published
- Record last updated
Affected versions
- Kubernetes Kubernetes
v1.13.6, v1.14.2
- k8s.io/kubernetes/cmd/kubeletGo
From 1.14.0 · fixed in 1.14.3
- k8s.io/kubernetes/cmd/kubeletGo
From 1.13.0 · fixed in 1.13.7
- k8s.io/kubernetesGo
From 1.13.0 · fixed in 1.13.7; From 1.14.0 · fixed in 1.14.3