Pod is running with added capabilities 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.
Containers/ Capabilities
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-Kubernetes
- Snyk IDSNYK-CC-00657
- creditSnyk Research Team
Description
Adding capabilities beyond the default set increases the risk of container breakout attacks. In most cases applications are able to operate normally with all Linux capabilities dropped, or with the default set of capabilities.
How to fix?
Remove the added capabilities attribute in spec.containers.securityContext.
Example Configuration
apiVersion: v1
kind: Pod
metadata:
name: valid2
spec:
containers:
- name: sec-ctx-4
image: gcr.io/google-samples/node-hello:1.0
securityContext:
capabilities:
drop:
- ALL
Remove the capabilities attribute in spec.container.security_context.
Example Configuration
resource "kubernetes_pod" "example_pod" {
metadata {
name = "example-pod"
labels = {
app = "example"
}
}
spec {
container {
image = "nginx:latest"
name = "nginx"
port {
container_port = 80
}
}
}
}