Flux2 vulnerable to Denial of Service due to Improper use of metav1.Duration
fluxcd flux2
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fluxcd/flux2 Go |
|
|
| github.com/fluxcd/source-controller Go |
|
|
| github.com/fluxcd/kustomize-controller |
fluxcd flux2
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fluxcd/flux2 Go |
|
|
| github.com/fluxcd/source-controller Go |
|
|
| github.com/fluxcd/kustomize-controller |
|
|
| github.com/fluxcd/helm-controller Go |
|
|
| github.com/fluxcd/notification-controller Go |
|
|
| github.com/fluxcd/image-automation-controller Go |
|
|
| github.com/fluxcd/image-reflector-controller Go |
|
|
| github.com/fluxcd/helm-controller/api Go |
|
|
| github.com/fluxcd/image-automation-controller/api Go |
|
|
| github.com/fluxcd/image-reflector-controller/api Go |
|
|
| github.com/fluxcd/kustomize-controller/api Go |
|
|
| github.com/fluxcd/notification-controller/api Go |
|
|
| github.com/fluxcd/source-controller/api Go |
|
|
Flux is an open and extensible continuous delivery solution for Kubernetes. Versions prior to 0.35.0 are subject to a Denial of Service. Users that have permissions to change Flux’s objects, either through a Flux source or directly within a cluster, can provide invalid data to fields `.spec.interval` or `.spec.timeout` (and structured variations of these fields), causing the entire object type to stop being processed. This issue is patched in version 0.35.0. As a workaround, Admission controllers can be employed to restrict the values that can be used for fields `.spec.interval` and `.spec.timeout`, however upgrading to the latest versions is still the recommended mitigation.
From the CVE record · GitHub_M
Flux versions before 0.35.0 can stop processing an entire object type when invalid values are supplied in `.spec.interval`, `.spec.timeout`, or their structured variations. An attacker needs permission to change Flux objects through a Flux source or directly in a cluster; no other user interaction is described.
Teams running Flux before 0.35.0 or any of the affected Go controller and API packages below their listed fixed versions should check their deployments.