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

> Kubernetes kubelet may run containers as root on restart or if image is cached, allowing privilege escalation if mustRunAsNonRoot is not set.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Aug 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r76g-g87f-vw8f, GO-2024-2780

## 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 (Improper Check or Handling of Exceptional Conditions)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes/cmd/kubelet` | Go | From 1.13.0 | 1.13.7 |
| `k8s.io/kubernetes/cmd/kubelet` | Go | From 1.13.0 | 1.13.7 |
| `k8s.io/kubernetes/cmd/kubelet` | Go | From 1.14.0 | 1.14.3 |
| `k8s.io/kubernetes/cmd/kubelet` | Go | From 1.14.0 | 1.14.3 |
| `k8s.io/kubernetes` | Go | From 1.13.0 | 1.13.7, 1.14.3 |

Products: 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](https://insights.sbomify.com/CVE-2018-1002105/): Privilege Escalation in Kubernetes (critical 9.8)
- [CVE-2017-1000056](https://insights.sbomify.com/CVE-2017-1000056/): Kubernetes Privilege Escalation (critical 9.8)
- [CVE-2016-1906](https://insights.sbomify.com/CVE-2016-1906/): Authorization bypass in Openshift (critical 9.8)
- [CVE-2023-3676](https://insights.sbomify.com/CVE-2023-3676/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8)
- [CVE-2023-3955](https://insights.sbomify.com/CVE-2023-3955/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11245 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2019-11245 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes/cmd/kubelet (Go): affected from 1.13.0; fixed in 1.13.7
- k8s.io/kubernetes/cmd/kubelet (Go): affected from 1.13.0; fixed in 1.13.7
- k8s.io/kubernetes/cmd/kubelet (Go): affected from 1.14.0; fixed in 1.14.3
- k8s.io/kubernetes/cmd/kubelet (Go): affected from 1.14.0; fixed in 1.14.3
- k8s.io/kubernetes (Go): affected from 1.13.0; fixed in 1.13.7, 1.14.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11245/ (Markdown: https://insights.sbomify.com/CVE-2019-11245/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11245
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11245
- OSV: https://osv.dev/vulnerability/CVE-2019-11245

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11245/
Summaries are generated and may contain mistakes; the official description above is the record.