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.
References
- bugzilla.redhat.com/show_bug.cgi?id=1715726
- github.com/advisories/GHSA-r76g-g87f-vw8f
- github.com/kubernetes/kubernetes
- github.com/kubernetes/kubernetes/issues/78308
- github.com/kubernetes/kubernetes/pull/76665
- github.com/kubernetes/kubernetes/pull/76665/commits/26e3c8674e66f0d10170d34f5445f0aed207387f
- nvd.nist.gov/vuln/detail/CVE-2019-11245
- security.netapp.com/advisory/ntap-20190919-0003
Detect and mitigate CVE-2019-11245 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →