NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2024-3744 — azurefile-csi-driver

MEDIUMFix: kubernetes-sigs/azurefile-csi-driver@a1b7446

CVE-2024-3744 is a medium-severity (CVSS 6.5) CWE-532 vulnerability in sigs.k8s.io/azurefile-csi-driver. A fix is available for sigs.k8s.io/azurefile-csi-driver — see the affected versions and patch details below.

Kubernetes azure-file-csi-driver in versions before 1.29.4 and 1.30.1 discloses service account tokens in logs

Also known asGHSA-qjqg-4wg7-957hGO-2024-2861
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2024-3744.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk
0.00%0.26%0.51%0.77%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹sigs.k8s.io/azurefile-csi-driver🐹sigs.k8s.io/azurefile-csi-driver

Real-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

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gosigs.k8s.io/azurefile-csi-driverall versions1.29.4go get sigs.k8s.io/azurefile-csi-driver@v1.29.4
🐹Gosigs.k8s.io/azurefile-csi-driver≥ 1.30.0&&< 1.30.11.30.1go get sigs.k8s.io/azurefile-csi-driver@v1.30.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sigs.k8s.io/azurefile-csi-driver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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 CVE-2024-3744 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-3744 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2024-3744: azurefile-csi-driver — Fixed in 1.29.4