Policy allows all capabilities 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/ 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-ControlsCSA-CCM
- Snyk IDSNYK-CC-00636
- creditSnyk Research Team
Description
The whitelist of allowed capability is set to all.
How to fix?
Remove allowedCapabilities attribute, or set value to [].
Example Configuration
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: demo
spec:
seLinux:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
runAsUser:
rule: RunAsAny
fsGroup:
rule: RunAsAny
requiredDropCapabilities:
- ALL
allowedCapabilities:
- []
Remove allowed_capabilities attribute, or set value to [].
Example Configuration
resource "kubernetes_pod_security_policy" "allowed" {
metadata {
name = "terraform-example"
}
spec {
privileged = false
allow_privilege_escalation = false
volumes = [
"configMap",
"emptyDir",
"projected",
"secret",
"downwardAPI",
"persistentVolumeClaim",
]
run_as_user {
rule = "MustRunAsNonRoot"
}
se_linux {
rule = "RunAsAny"
}
supplemental_groups {
rule = "MustRunAs"
range {
min = 1025
max = 65535
}
}
fs_group {
rule = "MustRunAs"
range {
min = 1025
max = 65535
}
}
allowed_capabilities = []
read_only_root_filesystem = true
}
}