Skip to content
Fencer Vulns
medium 4.9

CVE-2019-11245 json

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

published 2019-08-29 7 y ago modified 2026-06-17 4 mo ago also GHSA-r76g-g87f-vw8f , GO-2024-2780 , EUVD-2024-1293

cvss
4.9
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • go k8s.io/kubernetes/cmd/kubelet 1.13.7, 1.14.3
  • go k8s.io/kubernetes 1.13.7, 1.14.3
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250807T150727-1.1

opensuse advisories openSUSE-SU-2025:15424-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-11245 updated cvss 4.9

kubernetes: container uid changes to root after first restart

  • Red Hat OpenShift Container Platform 3.6 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +9 more Red Hat OpenShift Container Platform 3.7 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +10 more Red Hat OpenShift Container Platform 3.9 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +8 more Red Hat OpenShift Container Platform 3.10 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more Red Hat OpenShift Container Platform 3.11 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more Red Hat OpenShift Container Platform 4 openshift, openshift-clients, openshift-kubelet, openshift-hyperkube, openshift-kube-apiserver, openshift-kube-scheduler, +2 more
    +1 more products
    Red Hat Storage 3 heketi, heketi-client, python-heketi
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/kubernetes/kubernetes/issues/78308 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 4.9 CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 4.9 CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go k8s.io/kubernetes/cmd/kubelet
>=1.14.0, <1.14.3
>=1.13.0, <1.13.7
1.14.3
1.13.7
go k8s.io/kubernetes
>=1.13.0, <1.13.7
>=1.14.0, <1.14.3
1.13.7
1.14.3

Affected products

  • Kubernetes Kubernetes

Classification

Weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-266 Incorrect Privilege Assignment
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.