CVE-2019-11245CWE-703

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

Medium · published August 29, 2019

CVSS v3.0
4.9
EPSS
1%
Percentile
48.0
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.0
4.9 · MEDIUM
Vector
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS v4.0
Not supplied
EPSS
0.00599 · 48.0th percentile
Weakness
CWE-703 · Improper Check or Handling of Exceptional Conditions
Published
2019-08-29T00:22Z
EPSS history
Timeline
  • 29 AUG 00:22Z
    kubelet-started container uid changes to root after first restart or if image is already pulled to the node
    cvelistv5