Title

Kubernetes Kubelet must have the SSL Certificate Authority set. (Cat II impact)

Discussion

Kubernetes container and pod configuration are maintained by Kubelet. Kubelet agents register nodes with the API Server, mount volume storage, and perform health checks for containers and pods. Anyone who gains access to Kubelet agents can effectively control applications within the pods and containers. Using authenticity protection, the communication can be protected against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. The communication session is protected by utilizing transport encryption protocols such as TLS. TLS provides the Kubernetes API Server with a means to authenticate sessions and encrypt traffic. To enable encrypted communication for Kubelet, the clientCAFile must be set. This parameter gives the location of the SSL Certificate Authority file used to secure Kubelet communication.

Check Content

On the Control Plane, run the command: ps -ef | grep kubelet If the "--client-ca-file" option exists, this is a finding. Note the path to the config file (identified by --config). Run the command: grep -i clientCAFile <path_to_config_file> If the setting "clientCAFile" is not set or contains no value, this is a finding.

Fix Text

On the Control Plane, run the command: ps -ef | grep kubelet Remove the "--client-ca-file" option if present. Note the path to the config file (identified by --config). Edit the Kubernetes Kubelet config file: Set the value of "clientCAFile" to a path containing an Approved Organizational Certificate. Restart the kubelet service using the following command: systemctl daemon-reload && systemctl restart kubelet

Additional Identifiers

Rule ID: SV-242420r918179_rule

Vulnerability ID: V-242420

Group Title: SRG-APP-000219-CTR-000550

Expert Comments

CCIs tied to check.

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