Improper path handling in Kustomization files allows for denial of service
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 cause a Denial of Service at the controller level. 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. Users are recommended to upgrade.
From the CVE record · GitHub_M
A path traversal vulnerability in kustomize-controller allows an attacker to cause a controller-level denial of service through a malicious `kustomization.yaml`. The input does not specify whether network access, authentication, or user interaction is required.
Teams running Go package `github.com/fluxcd/kustomize-controller` versions >=0.16.0 and <0.24.0 or `github.com/fluxcd/flux2` versions >=0.19.0 and <0.29.0 should check their deployments.