The built-in "cluster-admin" role is used Affecting Deployment service in Kubernetes
Severity Framework
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Snyk CCSS
Rule category
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
IAM/ Access
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsFrameworks
CIS-Kubernetes
- Snyk IDSNYK-CC-00650
- creditSnyk Research Team
Description
The "cluster-admin" role comes with super-user level access which can be used to manipulate all resources in the cluster. Avoid using this role unless absolutely necessary.
How to fix?
Set the name attribute in roleRef to a value other than cluster_admin.
Example Configuration
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: valid-rolebinding
subjects:
- kind: ServiceAccount
name: test
namespace: test-ns
roleRef:
kind: ClusterRole
name: not-cluster-admin
apiGroup: rbac.authorization.k8s.io
Set the name attribute in role_ref to a value other than cluster_admin.
Example Configuration
resource "kubernetes_cluster_role_binding" "allowed1" {
metadata {
name = "basic-role-binding"
}
role_ref {
api_group = "rbac.authorization.k8s.io"
kind = "ClusterRole"
name = "basicrole"
}
subject {
kind = "Group"
name = "system:authenticated"
api_group = "rbac.authorization.k8s.io"
}
}