CVE-2019-11245
CVE-2019-11245 · kubelet-started container uid changes to root after first restart or if image is already pulled to the node
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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 4.9 · Medium · EPSS 0.6%
- Published
- Updated
Stack: containers
Affected products and versions
kubernetes
- Versions
- v1.13.6: Affected
- v1.14.2: Affected
No fix published