CVE-2019-11245: Kubelet Incorrect Privilege Assignment
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.
Published Apr 24, 2024 · Updated Jun 10, 2024
Affected packages
k8s.io/kubernetes/cmd/kubelet
- Ecosystem
- Go
- Affected
- >= 1.14.0, < 1.14.3
- Fixed in
- 1.14.3
- Check
go list -m k8s.io/kubernetes/cmd/kubelet
k8s.io/kubernetes/cmd/kubelet
- Ecosystem
- Go
- Affected
- >= 1.13.0, < 1.13.7
- Fixed in
- 1.13.7
- Check
go list -m k8s.io/kubernetes/cmd/kubelet
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2019-11245
- https://github.com/kubernetes/kubernetes/issues/78308
- https://github.com/kubernetes/kubernetes/pull/76665
- https://github.com/kubernetes/kubernetes/pull/76665/commits/26e3c8674e66f0d10170d34f5445f0aed207387f
- https://bugzilla.redhat.com/show_bug.cgi?id=1715726
- https://security.netapp.com/advisory/ntap-20190919-0003
- https://github.com/advisories/GHSA-r76g-g87f-vw8f
- https://pkg.go.dev/vuln/GO-2024-2780
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
