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.
See doc/triage.md for instructions on how to triage this report.
modules:
- module: github.com/fluxcd/flux2
packages:
- package: flux2
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.
cves:
- CVE-2022-39272
references:
- web: https://github.com/fluxcd/flux2/security/advisories/GHSA-f4p5-x4vc-mh4v
- web: https://github.com/kubernetes/apimachinery/issues/131
CVE-2022-39272 references github.com/fluxcd/flux2, which may be a Go module.
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.References:
See doc/triage.md for instructions on how to triage this report.