CVE-2022-24877: Improper path handling in kustomization files allows path traversal
Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious kustomization.yaml allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user's CI/CD pipeline to validate kustomization.yaml files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.
Other sources
Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious kustomization.yaml allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege escalation in multi-tenancy deployments. Workarounds include automated tooling in the user's CI/CD pipeline to validate kustomization.yaml files conform with specific policies. This vulnerability is fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0.
Affected Software
Event History
Frequently Asked Questions
What is CVE-2022-24877?
CVE-2022-24877 is a vulnerability in Flux and Kustomize-controller that allows path traversal and potential privilege escalation in multi-tenancy deployments.
What is the severity of CVE-2022-24877?
CVE-2022-24877 has a severity level of critical with a CVSS score of 8.8.
Which software versions are affected by CVE-2022-24877?
Flux version up to 0.29.0 and Kustomize-controller version up to 0.24.0 are affected by CVE-2022-24877.
How can an attacker exploit CVE-2022-24877?
An attacker can exploit CVE-2022-24877 by using a malicious `kustomization.yaml` file to perform path traversal and expose sensitive data from the controller's pod filesystem.
Is there a fix available for CVE-2022-24877?
Yes, it is recommended to update Flux to version 0.29.0 or newer, and Kustomize-controller to version 0.24.0 or newer to mitigate CVE-2022-24877.