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.
Workaround:
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
Link | Tags |
---|---|
https://github.com/kubernetes/kubernetes/issues/78308 | exploit third party advisory patch |
https://security.netapp.com/advisory/ntap-20190919-0003/ |