Token disclosure via failed parameter marshaling
Published Sep 5, 2025 · Updated Sep 5, 2025
Sensitive-data exposure in Kubernetes Secrets Store Sync Controller before 0.0.2 allows local users to read service account tokens from logs. When provider-parameter marshaling fails, the manager's error path logs the parameter set, including csi.storage.k8s.io/serviceAccount.tokens. Access to controller logs is required, and exposed tokens can be exchanged with external cloud providers to retrieve vault secrets.
Summary
What happened
Sensitive-data exposure in Kubernetes Secrets Store Sync Controller before 0.0.2 allows local users to read service account tokens from logs. When provider-parameter marshaling fails, the manager's error path logs the parameter set, including csi.storage.k8s.io/serviceAccount.tokens. Access to controller logs is required, and exposed tokens can be exchanged with external cloud providers to retrieve vault secrets.
The record
- CVE
- CVE-2025-7445
- Published
- Sep 5, 2025
- Updated
- Sep 5, 2025
- Vendor
- Kubernetes
- Product
- Secrets Store Sync Controller
- Classifications
- CWE-532, CAPEC-233, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2025CVE publishedPublication date reported by the CVE source.
- Sep 5, 2025Record 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=0 <0.0.2
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