Fluxcd vulnerabilities
We track 4 vulnerabilities in Fluxcd products across 3 products. 4 are rated high or critical, and none are known to be exploited. The most recent was published on September 7, 2022.
Latest Fluxcd vulnerabilities
- 7.5 High severity
flux2: Allocation of Resources Without Limits or Throttling
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 v
- 7.8 High severity
flux2: Improper Limitation of a Pathname to a Restricted Directory
Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories), and automating updates to configuration when there is new code to deploy. Flux CLI allows users to deploy Flux components into a Kubernetes cluster vi
- 8.8 High severity
flux2: Improper Limitation of a Pathname to a Restricted Directory
Flux is an open and extensible continuous delivery solution for Kubernetes. Path Traversal in the kustomize-controller via a malicious `kustomization.yaml` allows an attacker to expose sensitive data from the controller’s pod filesystem and possibly privilege
- 9.9 Critical severity
flux2: Improper Control of Generation of Code
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 mult