Skip to content
OpenAdvisories
Medium · 4.9 CVE-2019-11245 EUVD-2024-1293GHSA-r76g-g87f-vw8fGO-2024-2780

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

Published Aug 29, 2019 · Updated Sep 16, 2024 · Assigned by kubernetes

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 products

VendorProductAffectedFixed
Kubernetes Kubernetes v1.13.6, v1.14.2 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Tumbleweed govulncheck-vulndb 0.0.20250807T150727-1.1 openSUSE-SU-2025:15424-1

Affected packages

EcosystemPackageAffectedFixedRecord
Go k8s.io/kubernetes >= 1.13.0, < 1.13.7 · >= 1.14.0, < 1.14.3 1.13.7, 1.14.3 GO-2024-2780
Go k8s.io/kubernetes/cmd/kubelet >= 1.14.0, < 1.14.3 1.14.3 GHSA-r76g-g87f-vw8f
Go k8s.io/kubernetes/cmd/kubelet >= 1.13.0, < 1.13.7 1.13.7 GHSA-r76g-g87f-vw8f

Advisories 1

References