source-controller leaks Azure Storage SAS token into logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2024-31216: 0.21% estimated exploitation activity in the next 30 days; percentile 11.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact When source-controller is 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. Patches This vulnerability was fixed in source-controller v1.2.5. Workarounds There is no workaround for this vulnerability except for using a different auth mechanism such as Azure Workload Identity. Credits This issue was reported and fixed by Jagpreet Singh Tamber (@jagpreetstamber) from the Azure Arc team. References https://github.com/fluxcd/source-controller/pull/1430 For more information If you have any questions or comments about this advisory: - Open an issue in the source-controller repository. - Contact us at the CNCF Flux Channel.

Published by the source

15 May 2024, 17:09 UTC

Last modified by the source

15 May 2024, 19:30 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v554-xwgw-hc3w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-31216

Advisory: source-controller leaks Azure Storage SAS token into logs
IDs: CVE-2024-31216, GHSA-v554-xwgw-hc3w
Record: https://patchnext.com/advisories/cve-2024-31216 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fluxcd/source-controller 1.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fluxcd/source-controller: affected < 1.2.5; fixed in 1.2.5

## Suggested inspection (read-only)
- Go github.com/fluxcd/source-controller: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fluxcd/source-controller.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v554-xwgw-hc3w (GitHub-reviewed advisory GHSA-v554-xwgw-hc3w lists affected ranges: Go github.com/fluxcd/source-controller >=0 <1.2.5)

Commands are suggestions: review each one before running it.