CVE-2022-39272

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

MEDIUM

4.3

CVSS Score

Published: October 21, 2022 at 12:00 AM UTC

Updated: June 17, 2026 at 04:58 AM UTC

7 products affected across 1 vendorFLUX2Kustomize ControllerSource Controller

Using flux2 by fluxcd?

Get instant alerts when new vulnerabilities affect flux2 - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM4.3

Exploit prediction

EPSS 0.8%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

FLUX2 · Fluxcd

95%

v < 0.35.00.1.0 ≤ v < 0.35.0

Affected range stops below 0.35.0, so it looks safe — our inference, not a vendor statement

Helm Controller · Fluxcd

95%

0.0.2 ≤ v < 0.24.00.0.1 alpha1 0.0.1 alpha2 0.0.1 beta1 0.0.1 beta2 0.0.1 beta3 0.0.1 beta4

Affected range stops below 0.24.0, so it looks safe — our inference, not a vendor statement

Image Automation Controller · Fluxcd

95%

0.1.0 ≤ v < 0.26.0

Affected range stops below 0.26.0, so it looks safe — our inference, not a vendor statement

Image Reflector Controller · Fluxcd

95%

0.1.0 ≤ v < 0.22.0

Affected range stops below 0.22.0, so it looks safe — our inference, not a vendor statement

Kustomize Controller · Fluxcd

95%

0.0.2 ≤ v < 0.29.00.0.1 alpha1 0.0.1 alpha2 0.0.1 alpha3 0.0.1 alpha4 0.0.1 alpha5 0.0.1 alpha6 0.0.1 alpha7 0.0.1 alpha8 0.0.1 alpha9 0.0.1 beta1 0.0.1 beta2

Affected range stops below 0.29.0, so it looks safe — our inference, not a vendor statement

Notification Controller · Fluxcd

95%

0.0.2 ≤ v < 0.27.00.0.1 alpha1 0.0.1 alpha2 0.0.1 beta1

Affected range stops below 0.27.0, so it looks safe — our inference, not a vendor statement

Source Controller · Fluxcd

95%

0.0.2 ≤ v < 0.30.00.0.1 alpha1 0.0.1 alpha2 0.0.1 alpha3 0.0.1 alpha4 0.0.1 alpha5 0.0.1 alpha6 0.0.1 beta1 0.0.1 beta2

Affected range stops below 0.30.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/kubernetes/apimachinery/issues/131

References (2)

Third Party Advisory

Source: [email protected]

https://github.com/fluxcd/flux2/security/advisories/GHSA-f4p5-x4vc-mh4v

Issue TrackingPatchThird Party Advisory

Source: [email protected]

https://github.com/kubernetes/apimachinery/issues/131

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: LOW

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-1284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card