CVE-2022-36049: high-severity vulnerability in fluxcd flux2
Flux2 Helm Controller denial of service
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.7epss 1.5%
Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. In a shared cluster multi-tenancy environment, a tenant could create a HelmRelease that makes the controller panic, denying all other tenants from their Helm releases being reconciled. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Affected products
fluxcd · flux2Related CVEs — fluxcd flux2
In the same product, most dangerous first.
CVE-2022-24877CRITICALImproper path handling in kustomization files allows path traversalEPSS 1.2%CVE-2022-24817CRITICALImproper kubeconfig validation allows arbitrary code executionEPSS 1.1%CVE-2022-24878HIGHImproper path handling in Kustomization files allows for denial of serviceEPSS 1.0%CVE-2022-39272MEDIUMFlux2 vulnerable to Denial of Service due to Improper use of metav1.DurationEPSS 0.8%CVE-2022-36035HIGHFlux CLI Workload InjectionEPSS 0.3%