CVE-2019-11245: kubelet-started container uid changes to root after first restart or if image is already pulled to the node
First published: Fri May 24 2019(Updated: )
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.
Credit: jordan@liggitt.net jordan@liggitt.net
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Kubernetes Kubernetes | =1.13.6 | |
| Kubernetes Kubernetes | =1.14.2 | |
| go/k8s.io/kubernetes/cmd/kubelet | >=1.13.0<1.13.7 | 1.13.7 |
| go/k8s.io/kubernetes/cmd/kubelet | >=1.14.0<1.14.3 | 1.14.3 |
| redhat/kubernetes | <1.13.7 | 1.13.7 |
| redhat/kubernetes | <1.14.3 | 1.14.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/kubernetes/kubernetes/issues/78308
- https://security.netapp.com/advisory/ntap-20190919-0003/
- https://github.com/rancher/k3s/issues/511
- https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
- https://github.com/kubernetes/kubernetes/pull/78261
- https://github.com/kubernetes/kubernetes/pull/78320
- https://github.com/kubernetes/kubernetes/pull/78316
- https://github.com/kubernetes/kubernetes/pull/76665
- https://github.com/kubernetes/kubernetes/pull/77322
- https://github.com/kubernetes/kubernetes/pull/77320
- https://discuss.kubernetes.io/t/security-regression-in-kubernetes-kubelet-v1-13-6-and-v1-14-2-only-cve-2019-11245/6584
- https://bugzilla.redhat.com/show_bug.cgi?id=1715726
- https://nvd.nist.gov/vuln/detail/CVE-2019-11245
- https://github.com/kubernetes/kubernetes/pull/76665/commits/26e3c8674e66f0d10170d34f5445f0aed207387f
- https://security.netapp.com/advisory/ntap-20190919-0003
- https://github.com/advisories/GHSA-r76g-g87f-vw8f (Advisory)
- https://pkg.go.dev/vuln/GO-2024-2780
Frequently Asked Questions
What is CVE-2019-11245?
CVE-2019-11245 is a vulnerability in kubelet versions 1.13.6 and 1.14.2 that allows containers to run as root even if the pod specifies mustRunAsNonRoot: true.
How severe is CVE-2019-11245?
CVE-2019-11245 has a severity rating of 7.8 (high).
Which versions of Kubernetes are affected by CVE-2019-11245?
Kubernetes versions 1.13.6 and 1.14.2 are affected by CVE-2019-11245.
How can I fix CVE-2019-11245?
To fix CVE-2019-11245, upgrade to a version of kubelet that is not affected (e.g., versions higher than 1.14.2).
Are there any references for CVE-2019-11245?
Yes, you can find references for CVE-2019-11245 at the following links: [link1] [link2]
- collector/nvd-index
- agent/type
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2019-11245
- agent/software-canonical-lookup
- agent/weakness
- agent/author
- agent/remedy
- agent/severity
- agent/description
- collector/nvd-cve
- source/NVD
- agent/softwarecombine
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-r76g-g87f-vw8f
- agent/references
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/title
- agent/first-publish-date
- agent/event
- agent/tags
- agent/trending
- vendor/kubernetes
- canonical/kubernetes kubernetes
- version/kubernetes kubernetes/1.13.6
- version/kubernetes kubernetes/1.14.2
- package-manager/redhat
- package-manager/go