CVE-2019-11245

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

Published Aug 29, 2019 CVSS 3.0 · 4.9 Medium EPSS < 1% KEV · Not listed
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.

Remediation

Vendor Workaround

Specify runAsUser directives in pods to control the uid a container runs as. Specify mustRunAsNonRoot:true directives in pods to prevent starting as root (note this means the attempt to start the container will fail on affected kubelet versions).

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-1293 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.
Github GHSA Github GHSA GHSA-r76g-g87f-vw8f Kubelet Incorrect Privilege Assignment
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
kubernetes
Published
Updated
Sep 16, 2024, 10:09 PM
Reserved
Apr 17, 2019, 12:00 AM
Status
Modified
Published
Aug 29, 2019, 1:15 AM
Modified
Jun 17, 2026, 2:12 AM
Severity
Moderate
Public date
May 24, 2019, 12:00 AM