Fluxcd Source-controller 0.0.1 Beta 2
Approved changes feed: RSS · Atom
cpe:2.3:a:fluxcd:source-controller:0.0.1:beta2:*:*:*:*:*:*
part: a version: 0.0.1 update: beta2
| Vendor | Fluxcd (f6b8c53c-912a-5287-a474-b2f041f6616f) |
|---|---|
| Product | Source Controller (1fcbcc9d-65e9-5db5-aa87-40fe6517edbe) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/fluxcd/flux2 |
purl2cpe | 2026-06-01 10:12:37.461367 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-39272 |
vulnerable | 2026-06-08 05:47:18.508440 |
Flux2 vulnerable to Denial of Service due to Improper use of metav1.Duration
MEDIUM (5)
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.
Published: 2022-10-21T00:00:00.000Z
Updated: 2025-04-23T16:45:22.608Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.