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.
References
| Link | Resource |
|---|---|
| https://github.com/fluxcd/flux2/security/advisories/GHSA-f4p5-x4vc-mh4v | Third Party Advisory |
| https://github.com/kubernetes/apimachinery/issues/131 | Issue Tracking Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2022-10-22 00:15
Updated : 2023-11-07 03:50
NVD link : CVE-2022-39272
Mitre link : CVE-2022-39272
CVE.ORG link : CVE-2022-39272
JSON object : View
Products Affected
fluxcd
- image-reflector-controller
- notification-controller
- flux2
- source-controller
- kustomize-controller
- helm-controller
- image-automation-controller
CWE
CWE-1284
Improper Validation of Specified Quantity in Input