Security policy allows sharing of host's IPC namespace 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-ControlsCIS-Kubernetes
- Snyk IDSNYK-CC-00633
- creditSnyk Research Team
Description
Containers will be able to communicate with the host's shared channels which breaks the container security boundary.
How to fix?
Remove the hostIPC attribute, or set value to false.
Remove the host_ipc attribute, or set value to false.
Example Configuration
resource "kubernetes_pod_security_policy" "allowed" {
metadata {
name = "terraform-example"
}
spec {
host_ipc = false
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 = 1
max = 65535
}
}
fs_group {
rule = "MustRunAs"
range {
min = 1
max = 65535
}
}
read_only_root_filesystem = true
}
}