GHSA-rcw7-pqfp-735x — secrets-store-sync-contro…
MEDIUMGHSA-rcw7-pqfp-735x is a medium-severity (CVSS 6.5) CWE-532 vulnerability in sigs.k8s.io/secrets-store-sync-controller. A fix is available for sigs.k8s.io/secrets-store-sync-controller — see the affected versions and patch details below.
secrets-store-sync-controller discloses service account tokens in logs
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-rcw7-pqfp-735x.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-rcw7-pqfp-735x plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
sigs.k8s.io/secrets-store-sync-controllerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Hello Kubernetes Community,
A security issue was discovered in secrets-store-sync-controller where an actor with access to the controller logs could observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions. Tokens are only logged when there is a specific error marshaling the parameters sent to the providers.
Am I vulnerable?
To check if tokens are being logged, examine the manager container log:
kubectl logs -l 'app.kubernetes.io/part-of=secrets-store-sync-controller' -c manager -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens"
Affected Versions
- secrets-store-sync-controller < v0.0.2
How do I mitigate this vulnerability?
Upgrade to secrets-store-sync-controller v0.0.2+
Fixed Versions
- secrets-store-sync-controller >= v0.0.2
Detection
Examine cloud provider logs for unexpected token exchanges, as well as unexpected access to cloud vault secrets.
If you find evidence that this vulnerability has been exploited, please contact [email protected]
Acknowledgements
This vulnerability was reported by Reem Rotenberg and Kas Dekel from Microsoft.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | sigs.k8s.io/secrets-store-sync-controller | all versions | 0.0.2go get sigs.k8s.io/secrets-store-sync-controller@v0.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sigs.k8s.io/secrets-store-sync-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sigs.k8s.io/secrets-store-sync-controller to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcw7-pqfp-735x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rcw7-pqfp-735x can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rcw7-pqfp-735x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rcw7-pqfp-735x in your dependencies?
O3 Security finds GHSA-rcw7-pqfp-735x across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.