source-controller leaks theAzure Storage SAS token into logs on connection errors
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| fluxcd | source-controller | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Fluxcd | Source-controller | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1788 | 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. |
Github GHSA |
GHSA-v554-xwgw-hc3w | source-controller leaks Azure Storage SAS token into logs |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.213% probability within 30 days)
No history.