Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

cve-program · CVE-2022-39272

Published

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.

Read the publisher's advisory

euvd · EUVD-2022-7087

Published

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.

Read the publisher's advisory

nvd · CVE-2022-39272

Published

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.

Read the publisher's advisory

osv · GHSA-f4p5-x4vc-mh4v

Published

Flux controllers within the affected versions range 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` not being fully compatible with the Go type `time.Duration` as explained on [upstream report](https://github.com/kubernetes/apimachinery/issues/131); b) lack of validation within Flux to restrict allowed values. ### Workarounds 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. ### Credits This issue was reported by Alexander Block (@codablock) through the Flux security mailing list (as [recommended](https://fluxcd.io/security/#report-a-vulnerability)). ### For more information If you have any questions or comments about this advisory: - Open an issue in any of the affected repositories. - Contact us at the CNCF Flux channel. ### References - https://github.com/kubernetes/apimachinery/issues/131

Read the publisher's advisory

osv · GO-2022-1071

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2022-39272

Published

flux2

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "fluxcd",
                    "product": "flux2",
                    "versions": [
                        {
                            "version": "< 0.35.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2022-7087

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 21, 2022, 12:00:00 AM

dateUpdated: Apr 23, 2025, 4:45:22 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2022-39272

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-1284

Original publisher date fields

published: 2022-10-22T00:15:09.310

lastModified: 2026-06-17T04:58:02.757

35 source CPE criteria · context only
  • cpe:2.3:a:fluxcd:flux2:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:0.0.1:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:0.0.1:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:0.0.1:beta1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:0.0.1:beta2:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:0.0.1:beta3:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:helm-controller:0.0.1:beta4:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:image-automation-controller:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:image-reflector-controller:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha3:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha4:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha5:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha6:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha7:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha8:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:alpha9:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:beta1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:kustomize-controller:0.0.1:beta2:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:notification-controller:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:notification-controller:0.0.1:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:notification-controller:0.0.1:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:notification-controller:0.0.1:beta1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:*:*:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:alpha3:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:alpha4:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:alpha5:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:alpha6:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:beta1:*:*:*:*:*:*
  • cpe:2.3:a:fluxcd:source-controller:0.0.1:beta2:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-f4p5-x4vc-mh4v

Published

github.com/fluxcd/flux2

Go

SEMVER · introduced 0.1.0 → fixed 0.35.0

github.com/fluxcd/source-controller

Go

SEMVER · introduced 0.0.1-alpha-1 → fixed 0.30.0

github.com/fluxcd/kustomize-controller

Go

SEMVER · introduced 0.0.1-alpha-1 → fixed 0.29.0

github.com/fluxcd/helm-controller

Go

SEMVER · introduced 0.0.1-alpha-1 → fixed 0.24.0

github.com/fluxcd/notification-controller

Go

SEMVER · introduced 0.0.1-alpha-1 → fixed 0.27.0

github.com/fluxcd/image-automation-controller

Go

SEMVER · introduced 0.1.0 → fixed 0.26.0

github.com/fluxcd/image-reflector-controller

Go

SEMVER · introduced 0.1.0 → fixed 0.22.0

github.com/fluxcd/helm-controller/api

Go

SEMVER · introduced 0 → fixed 0.26.0

github.com/fluxcd/image-automation-controller/api

Go

SEMVER · introduced 0 → fixed 0.26.1

github.com/fluxcd/image-reflector-controller/api

Go

SEMVER · introduced 0 → fixed 0.22.1

github.com/fluxcd/kustomize-controller/api

Go

SEMVER · introduced 0 → fixed 0.30.0

github.com/fluxcd/notification-controller/api

Go

SEMVER · introduced 0 → fixed 0.28.0

github.com/fluxcd/source-controller/api

Go

SEMVER · introduced 0 → fixed 0.30.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2022-1071

Published

github.com/fluxcd/helm-controller/api

Go

SEMVER · introduced 0 → fixed 0.26.0

github.com/fluxcd/image-automation-controller/api

Go

SEMVER · introduced 0 → fixed 0.26.1

github.com/fluxcd/image-reflector-controller/api

Go

SEMVER · introduced 0 → fixed 0.22.1

github.com/fluxcd/kustomize-controller/api

Go

SEMVER · introduced 0 → fixed 0.30.0

github.com/fluxcd/notification-controller/api

Go

SEMVER · introduced 0 → fixed 0.28.0

github.com/fluxcd/source-controller/api

Go

SEMVER · introduced 0 → fixed 0.30.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current