Controller crash via recursive Kustomization references
Published May 6, 2022 · Updated Apr 23, 2025
Uncontrolled recursion in Flux 0.19.0 through 0.28.x allows remote authenticated users to crash kustomize-controller with a crafted file. A specially crafted kustomization.yaml uses path references that validation fails to block, causing the controller to enter an endless loop. Write access to a Flux source is required; in multi-tenant clusters, the crash prevents multiple tenants' Kustomizations from being applied.
Summary
What happened
Uncontrolled recursion in Flux 0.19.0 through 0.28.x allows remote authenticated users to crash kustomize-controller with a crafted file. A specially crafted kustomization.yaml uses path references that validation fails to block, causing the controller to enter an endless loop. Write access to a Flux source is required; in multi-tenant clusters, the crash prevents multiple tenants' Kustomizations from being applied.
The record
- CVE
- CVE-2022-24878
- Published
- May 6, 2022
- Updated
- Apr 23, 2025
- Vendor
- Flux CD
- Product
- Flux
- Classifications
- CWE-22, CWE-674, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=flux2 < v0.28.5, >= v0.19.0
- Affected versionversion=kustomize < v0.29.0, >= v0.16.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo