Denial of service in flux controllers in github.com/fluxcd modules
Flux controllers are vulnerable to a denial of service attack. 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. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-39272US | medium4.3 | — | ||
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’… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-f4p5-x4vc-mh4vADVISORY
- https://github.com/fluxcd/helm-controller/pull/533FIX
- https://github.com/fluxcd/image-automation-controller/pull/439FIX
- https://github.com/fluxcd/image-reflector-controller/pull/314FIX
- https://github.com/fluxcd/kustomize-controller/pull/731FIX
- https://github.com/fluxcd/notification-controller/pull/420FIX
- https://github.com/fluxcd/source-controller/pull/903FIX
- https://github.com/kubernetes/apimachinery#131WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan