Azure SAS token disclosure via unsanitized errors
Published May 15, 2024 · Updated Aug 2, 2024
Sensitive-data exposure in Flux CD source-controller before 1.2.5 allows local users to read Azure Storage SAS tokens from logs. In bucket_controller.go, fetch error paths returned Azure client errors verbatim, preserving SAS query parameters when controllers logged reconciliation failures. Exploitation requires access to source-controller logs and an Azure-SAS-backed bucket that produces a connection error; the exposed token grants its configured Azure Blob Storage permissions until expiration.
Summary
What happened
Sensitive-data exposure in Flux CD source-controller before 1.2.5 allows local users to read Azure Storage SAS tokens from logs. In bucket_controller.go, fetch error paths returned Azure client errors verbatim, preserving SAS query parameters when controllers logged reconciliation failures. Exploitation requires access to source-controller logs and an Azure-SAS-backed bucket that produces a connection error; the exposed token grants its configured Azure Blob Storage permissions until expiration.
The record
- CVE
- CVE-2024-31216
- Published
- May 15, 2024
- Updated
- Aug 2, 2024
- Vendor
- Flux CD
- Product
- source-controller
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 15, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo