Pod stores secrets in environment variables Affecting Service 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-Kubernetes
- Snyk IDSNYK-CC-00658
- creditSnyk Research Team
Description
Any secrets stored in environment variables could be exposed if the environment is logged or otherwise exposed by an application. Providing access to secrets via volume mounts is preferred.
How to fix?
Ensure spec.containers.env.valueFrom attribute of pod doesn't contain secretKeyRef.
Example configuration:
apiVersion: v1
kind: Pod
metadata:
name: valud-pod
spec:
containers:
- name: mysql
image: mysql:8.0
volumeMounts:
- name: mysql-pass
mountPath: "/etc//mysql/credentials"
volumes:
- name: mysql-pass
secret:
secretName: basic-auth
Set the spec.container.volume.secret attribute in kubernetes_pod.
Example configuration:
resource "kubernetes_pod" "allowed1" {
metadata {
name = "example"
}
spec {
container {
image = "mysql:8.0"
name = "mysql"
volume_mount {
mount_path = "/etc//mysql/credentials"
name = "mysql-pass"
}
}
volume {
name = "mysql-pass"
secret {
secret_name = "basic-auth"
}
}
}
}