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.
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
Fixes

Solution

No solution given by the 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).

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: kubernetes

Published:

Updated: 2024-09-16T22:09:44.877Z

Reserved: 2019-04-17T00:00:00

Link: CVE-2019-11245

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-08-29T01:15:11.147

Modified: 2024-11-21T04:20:47.757

Link: CVE-2019-11245

cve-icon Redhat

Severity : Moderate

Publid Date: 2019-05-24T00:00:00Z

Links: CVE-2019-11245 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses