Improper path handling in kustomization files allows path traversal
fluxcd flux2
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fluxcd/kustomize-controller Go |
|
|
| github.com/fluxcd/flux2 Go |
|
|
fluxcd flux2
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fluxcd/kustomize-controller Go |
|
|
| github.com/fluxcd/flux2 Go |
|
|
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.
From the CVE record · GitHub_M
A path traversal vulnerability in Flux's kustomize-controller can be triggered by a malicious `kustomization.yaml`. An attacker who can supply that file may expose sensitive data from the controller pod's filesystem and possibly escalate privileges in multi-tenant deployments. The input does not specify authentication requirements.
Teams running Go package github.com/fluxcd/kustomize-controller before 0.24.0 or github.com/fluxcd/flux2 before 0.29.0 should check their deployments.