Source Controller
Approved changes feed: RSS · Atom
cpe:2.3:a:fluxcd:source-controller:*:*:*:*:*:*:*:*
part: a version: * update: *
| 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 purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/fluxcd/flux2 |
purl2cpe | 2026-06-01 10:12:37.461356 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-31216 |
vulnerable | 2026-06-08 06:35:31.115992 |
source-controller leaks theAzure Storage SAS token into logs on connection errors
MEDIUM (5.1)
The source-controller is a Kubernetes operator, specialised in artifacts acquisition from external sources such as Git, OCI, Helm repositories and S3-compatible buckets. The source-controller implements the source.toolkit.fluxcd.io API and is a core component of the GitOps toolkit. Prior to version 1.2.5, when source-controller was configured to use an Azure SAS token when connecting to Azure Blob Storage, the token was logged along with the Azure URL when the controller encountered a connection error. An attacker with access to the source-controller logs could use the token to gain access to the Azure Blob Storage until the token expires. This vulnerability was fixed in source-controller v1.2.5. There is no workaround for this vulnerability except for using a different auth mechanism such as Azure Workload Identity.
Published: 2024-05-15T15:52:15.084Z
Updated: 2024-08-02T01:46:04.808Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-39272 |
vulnerable | 2026-06-08 05:47:18.503367 |
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.