Improper kubeconfig validation allows arbitrary code execution
fluxcd flux2
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fluxcd/flux2 Go |
|
|
| github.com/fluxcd/kustomize-controller Go |
|
|
| github.com/fluxcd/helm-controller |
fluxcd flux2
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fluxcd/flux2 Go |
|
|
| github.com/fluxcd/kustomize-controller Go |
|
|
| github.com/fluxcd/helm-controller |
|
|
Flux2 is an open and extensible continuous delivery solution for Kubernetes. Flux2 versions between 0.1.0 and 0.29.0, helm-controller 0.1.0 to v0.19.0, and kustomize-controller 0.1.0 to v0.23.0 are vulnerable to Code Injection via malicious Kubeconfig. In multi-tenancy deployments this can also lead to privilege escalation if the controller's service account has elevated permissions. Workarounds include disabling functionality via Validating Admission webhooks by restricting users from setting the `spec.kubeConfig` field in Flux `Kustomization` and `HelmRelease` objects. Additional mitigations include applying restrictive AppArmor and SELinux profiles on the controller’s pod to limit what binaries can be executed. This vulnerability is fixed in kustomize-controller v0.23.0 and helm-controller v0.19.0, both included in flux2 v0.29.0
From the CVE record · GitHub_M
Flux2’s kustomize-controller and helm-controller are vulnerable to code injection through a malicious Kubeconfig. In multi-tenant deployments, this can also lead to privilege escalation if the controller’s service account has elevated permissions. The input does not specify network access, authentication, or user-interaction requirements.
Check deployments using Go package github.com/fluxcd/flux2 versions >=0.1.0 <0.29.0, github.com/fluxcd/kustomize-controller versions >=0.1.0 <0.23.0, or github.com/fluxcd/helm-controller versions >=0.2.0 <0.19.0.