VYPR
Moderate severityNVD Advisory· Published Aug 29, 2019· Updated Sep 16, 2024

kubelet-started container uid changes to root after first restart or if image is already pulled to the node

CVE-2019-11245

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.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
k8s.io/kubernetes/cmd/kubeletGo
>= 1.14.0, < 1.14.31.14.3
k8s.io/kubernetes/cmd/kubeletGo
>= 1.13.0, < 1.13.71.13.7

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

9

News mentions

0

No linked articles in our index yet.