Vulnerabilities · 2022 · Helm
CVE-2022-36049
Helm vulnerability
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.
Affected products
Helm, Flux2, Helm-controller. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Helm runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugs.chromium.org/p/oss-fuzz/issues/detail?id=44996 · Third Party Advisory
- bugs.chromium.org/p/oss-fuzz/issues/detail?id=48360 · Third Party Advisory
- github.com/fluxcd/flux2/security/advisories/GHSA-p2g7-xwvr-rrw3 · Third Party Advisory
- github.com/helm/helm/security/advisories/GHSA-7hfp-qfw3-5jxh · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-36049
- cve.org/CVERecord?id=CVE-2022-36049
More vulnerabilities in Helm products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.