Описание
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.
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
cosmic | not-affected | code not present |
devel | not-affected | code not present |
disco | not-affected | code not present |
esm-infra-legacy/trusty | DNE | |
precise/esm | DNE | |
trusty | ignored | end of standard support |
trusty/esm | DNE | |
upstream | not-affected | debian: Vulnerable code not present |
xenial | DNE |
Показывать по
EPSS
4.6 Medium
CVSS2
4.9 Medium
CVSS3
Связанные уязвимости
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.
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.
In kubelet v1.13.6 and v1.14.2, containers for pods that do not specif ...
EPSS
4.6 Medium
CVSS2
4.9 Medium
CVSS3