Title

Kubernetes must remove old components after updated versions have been installed. (Cat II impact)

Discussion

Previous versions of Kubernetes components that are not removed after updates have been installed may be exploited by adversaries by allowing the vulnerabilities to still exist within the cluster. It is important for Kubernetes to remove old pods when newer pods are created using new images to always be at the desired security state.

Check Content

To view all pods and the images used to create the pods, from the Control Plane, run the following command: kubectl get pods --all-namespaces -o jsonpath="{..image}" | \ tr -s '[[:space:]]' '\n' | \ sort | \ uniq -c Review the images used for pods running within Kubernetes. If there are multiple versions of the same image, this is a finding.

Fix Text

Remove any old pods that are using older images. On the Control Plane, run the command: kubectl delete pod podname (Note: "podname" is the name of the pod to delete.)

Additional Identifiers

Rule ID: SV-242442r961677_rule

Vulnerability ID: V-242442

Group Title: SRG-APP-000454-CTR-001110

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.