Improper kubeconfig validation allows arbitrary code execution
Description
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
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
github.com/fluxcd/flux2Go | >= 0.1.0, < 0.29.0 | 0.29.0 |
github.com/fluxcd/kustomize-controllerGo | >= 0.1.0, < 0.23.0 | 0.23.0 |
github.com/fluxcd/helm-controllerGo | >= 0.2.0, < 0.19.0 | 0.19.0 |
Affected products
6- osv-coords5 versionspkg:bitnami/fluxpkg:bitnami/kustomizepkg:golang/github.com/fluxcd/flux2pkg:golang/github.com/fluxcd/helm-controllerpkg:golang/github.com/fluxcd/kustomize-controller
>= 0.1.0, < 0.29.0+ 4 more
- (no CPE)range: >= 0.1.0, < 0.29.0
- (no CPE)range: >= 0.1.0, < 0.23.0
- (no CPE)range: >= 0.1.0, < 0.29.0
- (no CPE)range: >= 0.2.0, < 0.19.0
- (no CPE)range: >= 0.1.0, < 0.23.0
Patches
Vulnerability mechanics
References
3- github.com/advisories/GHSA-vvmq-fwmg-2gjcghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2022-24817ghsaADVISORY
- github.com/fluxcd/flux2/security/advisories/GHSA-vvmq-fwmg-2gjcghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.