Metrics
Affected Vendors & Products
Solution
Prior to upgrading, this vulnerability can be mitigated by running azure-file-csi-driver at log level 0 or 1 via the -v flag. To upgrade, refer to the documentation: https://github.com/kubernetes-sigs/azurefile-csi-driver?tab=readme-ov-file#install-driver-on-a-kubernetes-cluster
Workaround
No workaround given by the vendor.
Thu, 13 Feb 2025 18:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Thu, 13 Feb 2025 18:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | 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. |

Status: PUBLISHED
Assigner: kubernetes
Published:
Updated: 2025-02-13T17:52:59.394Z
Reserved: 2024-04-12T19:54:26.953Z
Link: CVE-2024-3744

Updated: 2024-08-01T20:20:01.141Z

Status : Awaiting Analysis
Published: 2024-05-15T01:15:07.843
Modified: 2025-02-13T18:18:10.853
Link: CVE-2024-3744


No data.