← Übersicht Flux

Flux2 vulnerable to Denial of Service due to Improper use of metav1.Duration

CVE-2022-39272 · ALPINE-CVE-2022-39272 · BIT-flux-2022-39272 · BIT-kustomize-2022-39272 · GHSA-f4p5-x4vc-mh4v · GO-2022-1071

Mittel · CVSS 5.0 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
19.10.2022 20:40
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
0.8 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Betroffene Pakete im beobachteten Stack

CVEfluxcd/flux2kein Fix bekanntCVE-2022-39272
Gogithub.com/fluxcd/flux20.1.0 → 0.35.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/helm-controller0.0.1-alpha-1 → 0.24.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/helm-controller/api0.26.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/helm-controller/api0.26.0GO-2022-1071
Gogithub.com/fluxcd/image-automation-controller0.1.0 → 0.26.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/image-automation-controller/api0.26.1GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/image-automation-controller/api0.26.1GO-2022-1071
Gogithub.com/fluxcd/image-reflector-controller0.1.0 → 0.22.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/image-reflector-controller/api0.22.1GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/image-reflector-controller/api0.22.1GO-2022-1071
Gogithub.com/fluxcd/kustomize-controller0.0.1-alpha-1 → 0.29.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/kustomize-controller/api0.30.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/kustomize-controller/api0.30.0GO-2022-1071
Gogithub.com/fluxcd/notification-controller0.0.1-alpha-1 → 0.27.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/notification-controller/api0.28.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/notification-controller/api0.28.0GO-2022-1071
Gogithub.com/fluxcd/source-controller0.0.1-alpha-1 → 0.30.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/source-controller/api0.30.0GHSA-f4p5-x4vc-mh4v
Gogithub.com/fluxcd/source-controller/api0.30.0GO-2022-1071
Weitere betroffene Pakete (13)
Alpine:v3.21flux0.36.0-r0ALPINE-CVE-2022-39272
Alpine:v3.22flux0.36.0-r0ALPINE-CVE-2022-39272
Alpine:v3.23flux0.36.0-r0ALPINE-CVE-2022-39272
Alpine:v3.24flux0.36.0-r0ALPINE-CVE-2022-39272
Bitnamiflux0.1.0 → 0.35.0BIT-flux-2022-39272
Bitnamikustomize0.0.2 → 0.29.0BIT-kustomize-2022-39272
NVDfluxcd:flux20.1.0 → 0.35.0CVE-2022-39272
NVDfluxcd:helm-controller0.0.2 → 0.24.0CVE-2022-39272
NVDfluxcd:image-automation-controller0.1.0 → 0.26.0CVE-2022-39272
NVDfluxcd:image-reflector-controller0.1.0 → 0.22.0CVE-2022-39272
NVDfluxcd:kustomize-controller0.0.2 → 0.29.0CVE-2022-39272
NVDfluxcd:notification-controller0.0.2 → 0.27.0CVE-2022-39272
NVDfluxcd:source-controller0.0.2 → 0.30.0CVE-2022-39272

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.