GHSA-jhjp-4c2q-xmx4: k8saudit shipped rules do not detect privileged/sensitive settings on init or ephemeral containers
The k8saudit plugin’s per-container fields (ka.req.pod.containers.*) and the shipped k8s_audit_rules.yaml evaluated only requestObject.spec.containers. Security-relevant settings on a pod’s initContainers or ephemeralContainers were not inspected, so the shipped Create Privileged Pod rule did not fire for a privileged container placed in either list.
References
- github.com/advisories/GHSA-jhjp-4c2q-xmx4
- github.com/falcosecurity/plugins/commit/0adb9b3c7e2c8bad53f30d01c057e038b2afa5e1
- github.com/falcosecurity/plugins/pull/1400
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-aks/v0.6.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-eks/v0.12.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-gke/v0.9.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-ovh/v0.6.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit/v0.18.0
- github.com/falcosecurity/plugins/security/advisories/GHSA-jhjp-4c2q-xmx4
Code Behaviors & Features
Detect and mitigate GHSA-jhjp-4c2q-xmx4 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →