CVE-2019-11245
kubelet-started container uid changes to root after first restart or if image is already pulled to the node
- State
- Published
- Severity
- 4.9 Medium
- Published
- Aug 29, 2019
- Updated
- Sep 16, 2024
- Reserved
- Apr 17, 2019
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.0 | 4.9 Medium | CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | kubernetes |
Weaknesses
- CWE-703 Improper Check or Handling of Exceptional Conditions
Affected Products
| Product | Versions |
|---|---|
KubernetesKubernetes |
|
References
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.