CVE-2019-11245: kubelet-started container uid changes to root after first restart or if image is already pulled to the node
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.
Other sources
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.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is CVE-2019-11245?
CVE-2019-11245 is a vulnerability in kubelet versions 1.13.6 and 1.14.2 that allows containers to run as root even if the pod specifies mustRunAsNonRoot: true.
How severe is CVE-2019-11245?
CVE-2019-11245 has a severity rating of 7.8 (high).
Which versions of Kubernetes are affected by CVE-2019-11245?
Kubernetes versions 1.13.6 and 1.14.2 are affected by CVE-2019-11245.
How can I fix CVE-2019-11245?
To fix CVE-2019-11245, upgrade to a version of kubelet that is not affected (e.g., versions higher than 1.14.2).
Are there any references for CVE-2019-11245?
Yes, you can find references for CVE-2019-11245 at the following links: [link1] [link2]