Role grants permissions to system reserved namespace Affecting RoleBinding service in Kubernetes
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
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 applications- Snyk IDSNYK-CC-00647
- creditSnyk Research Team
Description
A role was found that grant permission over system reserved namespace (either default or kube-system). Those namespaces should be used only by cluster operators, and should be treated as sensitive.
How to fix?
Set the namespaceattribute in subjects to a value other than default or kube-system.
Example configuration:
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: example-rolebinding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: admin
subjects:
- kind: ServiceAccount
name: default
namespace: example-namespace
Set different namespace and use it instead. Do not use default or kube-system in subject.namespace.
Example configuration:
resource "kubernetes_role_binding" "allowed" {
metadata {
name = "terraform-example"
}
role_ref {
api_group = "rbac.authorization.k8s.io"
kind = "Role"
name = "admin"
}
subject {
kind = "ServiceAccount"
name = "default"
namespace = "good-namespace"
}
}