https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 11:53:14 +0000 https://cve.radiocsirt.org/vuln/bit-flux-2022-39272 <p><strong>Affected:</strong> Bitnami: flux</p> <p>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.</p> <p><strong>Affected:</strong> Bitnami: flux</p> <p>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.</p> https://cve.radiocsirt.org/vuln/bit-flux-2022-39272 https://cve.radiocsirt.org/vuln/euvd-2026-233480 EUVD-2026-233480 https://cve.radiocsirt.org/vuln/euvd-2026-233480 https://cve.radiocsirt.org/vuln/fkie_cve-2022-39272 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-39272 https://cve.radiocsirt.org/vuln/ghsa-f4p5-x4vc-mh4v <p><strong>Affected:</strong> Go: github.com/fluxcd/flux2, Go: github.com/fluxcd/source-controller, Go: github.com/fluxcd/kustomize-controller, Go: github.com/fluxcd/helm-controller, Go: github.com/fluxcd/notification-controller, Go: github.com/fluxcd/image-automation-controller, Go: github.com/fluxcd/image-reflector-controller, Go: github.com/fluxcd/helm-controller/api, Go: github.com/fluxcd/image-automation-controller/api, Go: github.com/fluxcd/image-reflector-controller/api and 3 more</p> <p>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.</p> <p>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.</p> <p>### Workarounds</p> <p>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.</p> <p>### Credits</p> <p>This issue was reported by Alexander Block (@codablock) through the Flux security mailing list (as [recommended](https://fluxcd.io/security/#report-a-vulnerability)).</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory:</p> <p>- Open an issue in any of the affected repositories. - Contact us at the CNCF Flux channel.</p> <p>### References</p> <p>- https://github.com/kubernetes/apimachinery/issues/131</p> <p><strong>Affected:</strong> Go: github.com/fluxcd/flux2, Go: github.com/fluxcd/source-controller, Go: github.com/fluxcd/kustomize-controller, Go: github.com/fluxcd/helm-controller, Go: github.com/fluxcd/notification-controller, Go: github.com/fluxcd/image-automation-controller, Go: github.com/fluxcd/image-reflector-controller, Go: github.com/fluxcd/helm-controller/api, Go: github.com/fluxcd/image-automation-controller/api, Go: github.com/fluxcd/image-reflector-controller/api and 3 more</p> <p>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.</p> <p>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.</p> <p>### Workarounds</p> <p>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.</p> <p>### Credits</p> <p>This issue was reported by Alexander Block (@codablock) through the Flux security mailing list (as [recommended](https://fluxcd.io/security/#report-a-vulnerability)).</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory:</p> <p>- Open an issue in any of the affected repositories. - Contact us at the CNCF Flux channel.</p> <p>### References</p> <p>- https://github.com/kubernetes/apimachinery/issues/131</p> https://cve.radiocsirt.org/vuln/ghsa-f4p5-x4vc-mh4v https://cve.radiocsirt.org/vuln/gsd-2022-39272 gsd-2022-39272 https://cve.radiocsirt.org/vuln/gsd-2022-39272