Policy does not prevent use of root group Affecting Pod Security Policy 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/ Security
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-Controls
- Snyk IDSNYK-CC-00638
- creditSnyk Research Team
Description
Policy explicitly allows RunAsAny group which allows container to run in root GID context.
How to fix?
Set runAsGroup.rule to MustRunAs and set a range which does not include GID 0.
Set run_as_group.rule to MustRunAs and set a range which does not include a min or max of 0.
Example configuration:
resource "kubernetes_pod_security_policy" "allowed" {
metadata {
name = "terraform-example"
}
spec {
privileged = false
allow_privilege_escalation = false
run_as_user {
rule = "MustRunAsNonRoot"
}
se_linux {
rule = "RunAsAny"
}
run_as_group {
rule = "MustRunAs"
range {
min = 1
max = 65535
}
}
supplemental_groups {
rule = "MustRunAs"
range {
min = 1
max = 65535
}
}
fs_group {
rule = "MustRunAs"
range {
min = 1
max = 65535
}
}
read_only_root_filesystem = true
}
}