Title

The Kubernetes Kubelet must have the read-only port flag disabled. (Cat I impact)

Discussion

Kubelet serves a small REST API with read access to port 10255. The read-only port for Kubernetes provides no authentication or authorization security control. Providing unrestricted access on port 10255 exposes Kubernetes pods and containers to malicious attacks or compromise. Port 10255 is deprecated and should be disabled. Close the read-only-port by setting the API server's read-only port flag to "0".

Check Content

Run the following command on each Worker Node: ps -ef | grep kubelet Verify that the --read-only-port argument exists and is set to "0". If the --read-only-port argument exists and is not set to "0", this is a finding. If the --read-only-port argument does not exist, check the Control Plane Kubelet config file: On the Kubernetes Control Plane, run the command: ps -ef | grep kubelet Check the config file (path identified by: --config). Verify there is a readOnlyPort entry in the config file and it is set to "0". If the readOnlyPort argument exists and is not set to "0" this is a finding. If "--read-only-port=0" argument does not exist on the worker nodes and "readOnlyPort=0" does not exist on the Control Plane, this is a finding.

Fix Text

Edit the Kubernetes Kubelet file in the --config directory on the Kubernetes Control Plane: Set "readOnlyPort=0" If using worker node arguments, edit the kubelet service file (identified in the --config directory): On each Worker Node: set the parameter in KUBELET_SYSTEM_PODS_ARGS variable to "--read-only-port=0". Reset Kubelet service using the following command: service kubelet restart

Additional Identifiers

Rule ID: SV-242387r879530_rule

Vulnerability ID: V-242387

Group Title: SRG-APP-000033-CTR-000095

Expert Comments

CCIs tied to check.

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