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

What is CVE-2019-11245?

CVE-2019-11245 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 29 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-264, CWE-703

Which versions are affected by CVE-2019-11245?

5 open source packages ship an affected version, including k8s.io/kubernetes/cmd/kubelet and k8s.io/kubernetes. It affects 1 product.

Products include Kubernetes Kubernetes.

How do I fix CVE-2019-11245?

Upgrade k8s.io/kubernetes/cmd/kubelet to a fixed version for your release line: 1.13.7 or 1.14.3.

Is CVE-2019-11245 being exploited?

There is no known exploitation of CVE-2019-11245 in the wild and no public exploit code.

Other vulnerabilities in Kubernetes Kubernetes

• CVE-2018-1002105 Privilege Escalation in Kubernetes Critical 9.8
• CVE-2017-1000056 Kubernetes Privilege Escalation Critical 9.8
• CVE-2016-1906 Authorization bypass in Openshift Critical 9.8
• CVE-2023-3676 Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation High 8.8
• CVE-2023-3955 Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation High 8.8

All Kubernetes Kubernetes vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-r76g-g87f-vw8f, GO-2024-2780.