Container is running in privileged mode 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/ 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-ControlsCIS-KubernetesCSA-CCM
- Snyk IDSNYK-CC-00605
- creditSnyk Research Team
Description
Compromised container could potentially modify the underlying host kernel by loading unauthorized modules (i.e. drivers).
How to fix?
Remove securityContext.privileged attribute, or set value to false.
Example Configuration
apiVersion: v1
kind: Pod
metadata:
name: myapp-pod
labels:
app: myapp
spec:
containers:
- name: myapp-container
image: busybox
command: ['sh', '-c', 'echo Hello Kubernetes! && sleep 3600']
securityContext:
privileged: false
Remove security_context.privileged attribute, or set value to false.
Example Configuration
resource "kubernetes_pod" "allowed" {
metadata {
name = "terraform-example-1"
}
spec {
container {
image = "nginx:1.7.9"
name = "example"
env {
name = "environment"
value = "test"
}
security_context {
privileged = false
}
}
}
}