GHSA-qjqg-4wg7-957h
MEDIUMGHSA-qjqg-4wg7-957h is a medium-severity (CVSS 6.5) CWE-532 vulnerability in sigs.k8s.io/azurefile-csi-driver. O3 Security confirms whether GHSA-qjqg-4wg7-957h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
azure-file-csi-driver leaks service account tokens in the logs
Blast Radius
sigs.k8s.io/azurefile-csi-driver🐹sigs.k8s.io/azurefile-csi-driverReal-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
A security issue was discovered in azure-file-csi-driver where an actor with access to the driver 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 TokenRequests is configured in the CSIDriver object and the driver is set to run at log level 2 or greater via the -v flag.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | sigs.k8s.io/azurefile-csi-driver | all versions | 1.29.4 |
| 🐹Go | sigs.k8s.io/azurefile-csi-driver | ≥ 1.30.0&&< 1.30.1 | 1.30.1 |
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/azurefile-csi-driver. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sigs.k8s.io/azurefile-csi-driver to 1.29.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjqg-4wg7-957h 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 pinpoints whether GHSA-qjqg-4wg7-957h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qjqg-4wg7-957h. 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-qjqg-4wg7-957h in your dependencies?
O3 detects GHSA-qjqg-4wg7-957h across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.