Title

Kubernetes Kubelet must not disable timeouts. (Cat II impact)

Discussion

Idle connections from the Kubelet can be used by unauthorized users to perform malicious activity to the nodes, pods, containers, and cluster within the Kubernetes Control Plane. Setting the streaming connection idle timeout defines the maximum time an idle session is permitted prior to disconnect. Setting the value to "0" never disconnects any idle sessions. Idle timeouts must never be set to "0" and should be defined at "5m" (the default is 4hr).

Check Content

Change to the /etc/sysconfig/ directory on the Kubernetes Master Node. Run the command: grep -i streaming-connection-idle-timeout kubelet If the setting streaming-connection-idle-timeout is set to < "5m" or the parameter is not configured in the Kubernetes Kubelet, this is a finding.

Fix Text

Edit the Kubernetes Kubelet file in the /etc/sysconfig directory on the Kubernetes Master Node. Set the argument "--streaming-connection-idle-timeout" to a value of "5m". Reset Kubelet service using the following command: service kubelet restart

Additional Identifiers

Rule ID: SV-245541r821621_rule

Vulnerability ID: V-245541

Group Title: SRG-APP-000190-CTR-000500

Expert Comments

CCIs tied to check.

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