CVE-2019-11245
kubelet-started container uid changes to root after first restart or if image is already pulled to the node
Vexday Risk Score
13Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 4.9EPSS 0.6%KEV nãoPoC —Patch —
Lifecycle
29 Aug 2019Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Affected products
Kubernetes · KubernetesWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →