Container does not drop all default capabilities Affecting Deployment 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-00610
- creditSnyk Research Team
Description
Containers are running with potentially unnecessary privileges violating the principle of least privilege.
How to fix?
Add ALL to securityContext.capabilities.drop list, and add only required capabilities in securityContext.capabilities.add.
Add ALL to spec.container.security_context.capabilities.drop list, and add only required capabilities to spec.container.security_context.capabilities.add ensuring it also does not contain ALL.
Example Configuration
resource "kubernetes_pod" "allowed" {
metadata {
name = "terraform-example610a"
}
spec {
container {
security_context {
capabilities {
drop = ["ALL"]
add = ["NET_ADMIN"]
}
}
image = "nginx:1.7.9"
name = "example"
port {
container_port = 8080
}
}
}
}