Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | Kubernetes | 1.13.6 |
Related Weaknesses (CWE)
References
- https://github.com/kubernetes/kubernetes/issues/78308ExploitPatchThird Party Advisory
- https://security.netapp.com/advisory/ntap-20190919-0003/
- https://github.com/kubernetes/kubernetes/issues/78308ExploitPatchThird Party Advisory
- https://security.netapp.com/advisory/ntap-20190919-0003/
FAQ
What is CVE-2019-11245?
CVE-2019-11245 is a vulnerability with a CVSS score of 4.9 (MEDIUM). 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...
How severe is CVE-2019-11245?
CVE-2019-11245 has been rated MEDIUM with a CVSS base score of 4.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2019-11245?
Check the references section above for vendor advisories and patch information. Affected products include: Kubernetes Kubernetes.