CNTR-K8-000340 - The Kubernetes API server must have the insecure bind address not set.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

By default, the API server will listen on two ports and addresses. One address is the secure address and the other address is called the 'insecure bind' address and is set by default to localhost. Any requests to this address bypass authentication and authorization checks. If this insecure bind address is set to localhost, anyone who gains access to the host on which the Control Plane is running can bypass all authorization and authentication mechanisms put in place and have full control over the entire cluster.

Close or set the insecure bind address by setting the API server's --insecure-bind-address flag to an IP or leave it unset and ensure that the --insecure-bind-port is not set.

Solution

Edit the Kubernetes API Server manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Control Plane. Remove the value for the --insecure-bind-address setting.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Kubernetes_V1R8_STIG.zip

Item Details

References: CAT|I, CCI|CCI-000213, Rule-ID|SV-242388r863964_rule, STIG-ID|CNTR-K8-000340, Vuln-ID|V-242388

Plugin: Unix

Control ID: 2e568f65bc00abb3fe18755a6c72bb75989d04cd3b7bc243a1edf73cf1f83a48