CVE-2025-7445
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-05

Last updated on: 2025-09-05

Assigner: Kubernetes

Description
Kubernetes secrets-store-sync-controller in versions before 0.0.2 discloses service account tokens in logs.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-05
Last Modified
2025-09-05
Generated
2026-05-07
AI Q&A
2025-09-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
kubernetes secrets-store-sync-controller 0.0.1
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-532 The product writes sensitive information to a log file.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-7445 is a vulnerability in Kubernetes secrets-store-sync-controller versions before 0.0.2 where service account tokens are accidentally logged when there is an error marshaling parameters sent to external cloud providers. These logged tokens could be accessed by an attacker with local access to the logs, who could then exchange the tokens with external cloud providers to gain unauthorized access to secrets stored in cloud vault solutions, posing a confidentiality risk. [1, 2]


How can this vulnerability impact me? :

This vulnerability can impact you by exposing service account tokens in logs, which an attacker with local access could use to access sensitive secrets stored in cloud vaults. This leads to a high confidentiality impact, potentially allowing unauthorized access to sensitive information without affecting system integrity or availability. [1, 2]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Administrators can detect this vulnerability by checking the manager container logs for entries containing service account tokens. The suggested command is: kubectl logs -l 'app.kubernetes.io/part-of=secrets-store-sync-controller' -c manager -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens". Additionally, detection can be enhanced by examining cloud provider logs for unexpected token exchanges and unauthorized access to cloud vault secrets. [1, 2]


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to upgrade the secrets-store-sync-controller to version 0.0.2 or later, where the vulnerability has been fixed. [1, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart