github.com/fluxcd/kustomize-controller
Affected
- introduced
0, fixed0.24.0(semver)
Fixed versions
0.24.0
Fix
- Fixed version
0.24.0go get github.com/fluxcd/[email protected]
Advisory
Also known as: BIT-flux-2022-24877, BIT-kustomize-2022-24877, CVE-2022-24877, GO-2022-0447
Improper path handling in kustomization files allows path traversal
The kustomize-controller enables the use of Kustomize’s functionality when applying Kubernetes declarative state onto a cluster. A malicious user can use built-in features and a specially crafted kustomization.yaml to expose sensitive data from the controller’s pod filesystem. In multi-tenancy deployments this can lead to privilege escalation if the controller's service account has elevated permissions.
Within the affected versions, users with write access to a Flux source are able to use built-in features to expose sensitive data from the controller’s pod filesystem using a malicious kustomization.yaml file.
This vulnerability was fixed in kustomize-controller v0.24.0 and included in flux2 v0.29.0 released on 2022-04-20. The changes introduce a new Kustomize file system implementation which ensures that all files being handled are contained within the Kustomization working directory, blocking references to any files that do not meet that requirement.
Automated tooling (e.g. conftest) could be employed as a workaround, as part of a user's CI/CD pipeline to ensure that their kustomization.yaml files conform with specific policies, blocking access to sensitive path locations.
Critical Basis: The source's own band: CRITICAL
0, fixed 0.24.0 (semver)0.24.0
0.24.0go get github.com/fluxcd/[email protected]0, fixed 0.29.0 (semver)0.29.0
0.29.0go get github.com/fluxcd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0