RoleBinding is set to the default service account 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.
Containers/ Best Practices
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-ControlsCIS-Kubernetes
- Snyk IDSNYK-CC-00644
- creditSnyk Research Team
Description
A binding was found between a role and the default service account. The use of the default service account is discouraged.
How to fix?
Set subjects.name to a service account other than default.
Example Configuration
apiVersion: v1
kind: Namespace
metadata:
name: user-1-namespace
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: role-binding-valid
namespace: user-1-namespace
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: role-grantor
subjects:
- kind: User
name: default
namespace: default
- kind: User
name: default
namespace: kube-system
Set subject.name to a service account other than default.
Example Configuration
resource "kubernetes_role_binding" "allowed" {
metadata {
name = "terraform-example644"
namespace = "default"
}
role_ref {
api_group = "rbac.authorization.k8s.io"
kind = "Role"
name = "admin"
}
subject {
kind = "ServiceAccount"
name = "test"
namespace = "kube-system"
api_group = "rbac.authorization.k8s.io"
}
}