Role with too wide permissions 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 Control
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-ControlsCSA-CCM
- Snyk IDSNYK-CC-00643
- creditSnyk Research Team
Description
The use of wildcard rights grants is likely to provide excessive rights to the Kubernetes API.
How to fix?
Remove any wildcards [*] from rules.verbs and rules.resources.
Example Configuration
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: allowed-role
rules:
- apiGroups: [""]
resources: ["pods"]
verbs: ["get", "watch", "list"]
Remove any wildcards [*] from rule.verbs and rule.resources.
Example Configuration
resource "kubernetes_role" "allowed" {
metadata {
name = "terraform-example"
labels = {
test = "MyRole"
}
}
rule {
api_groups = [""]
resources = ["pods"]
resource_names = ["foo"]
verbs = ["get", "list", "watch"]
}
rule {
api_groups = [""]
resources = ["pods"]
resource_names = ["foo"]
verbs = ["get", "list", "watch"]
}
}