Kubelet Incorrect Privilege Assignment
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-11245US | high7.8 | — | ||
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 pu… | ||||
02
references
External citations — patches, advisories, analysis.
- https://bugzilla.redhat.com/show_bug.cgi?id=1715726WEB
- https://github.com/advisories/GHSA-r76g-g87f-vw8fADVISORY
- https://github.com/kubernetes/kubernetesPACKAGE
- https://github.com/kubernetes/kubernetes/issues/78308WEB
- https://github.com/kubernetes/kubernetes/pull/76665WEB
- https://github.com/kubernetes/kubernetes/pull/76665/commits/26e3c8674e66f0d10170d34f5445f0aed207387fWEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-11245ADVISORY
- https://pkg.go.dev/vuln/GO-2024-2780WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan