CVE-2019-11245

unknown

Published 2024-04-24 · Modified 2026-03-03

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

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.

Predictions

Exploit likelihood

20%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

Debian Fixed 5 releases

Version	Status	Fixed in
trixie	Fixed	`0`
sid	Fixed	`0`
forky	Fixed	`0`
bullseye	Fixed	`0`
bookworm	Fixed	`0`

Package impact

Ecosystem	Package	Vulnerable	Fixed
Go	k8s.io/kubernetes/cmd/kubelet	`>=1.14.0,<1.14.3`	`1.14.3`
Go	k8s.io/kubernetes/cmd/kubelet	`>=1.13.0,<1.13.7`	`1.13.7`
Go	k8s.io/kubernetes	`>=1.14.0,<1.14.3`	`1.13.7`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.