CVE-2022-24817: Improper kubeconfig validation allows arbitrary code execution

Published May 6, 2022
·
Updated

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

Affected Software

3 affected components
fluxcd Flux2>=0.1.0<0.29.0
fluxcd Helm-controller>=0.2.0<0.19.0
fluxcd Kustomize-controller>=0.1.0<0.23.0

Event History

May 6, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-24817?

CVE-2022-24817 is a vulnerability in Flux2, helm-controller, and kustomize-controller that allows code injection via malicious Kubeconfig, potentially leading to remote code execution.

2

What is the severity of CVE-2022-24817?

CVE-2022-24817 has a severity rating of 9.9 (Critical).

3

Which versions of Flux2 are affected by CVE-2022-24817?

Flux2 versions between 0.1.0 and 0.29.0 are affected by CVE-2022-24817.

4

Which versions of helm-controller are affected by CVE-2022-24817?

helm-controller versions between 0.1.0 and 0.19.0 are affected by CVE-2022-24817.

5

Which versions of kustomize-controller are affected by CVE-2022-24817?

kustomize-controller versions between 0.1.0 and 0.23.0 are affected by CVE-2022-24817.

6

How can CVE-2022-24817 be exploited?

CVE-2022-24817 can be exploited by using a malicious Kubeconfig to inject code, potentially leading to remote code execution.

7

How can I fix CVE-2022-24817?

To fix CVE-2022-24817, it is recommended to update Flux2, helm-controller, and kustomize-controller to versions that are not vulnerable. Refer to the official advisory for more information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203