Advisory

GHSA-rcw7-pqfp-735x

Also known as: CVE-2025-7445, GO-2025-3939

Summary

secrets-store-sync-controller discloses service account tokens in logs

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-09-05 21:02 UTC
Modified
2025-09-17 17:27 UTC

Affected packages and fixes

sigs.k8s.io/secrets-store-sync-controller

Go · All systems

Affected

  • introduced 0, fixed 0.0.2 (semver)

Fixed versions

0.0.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences