Information Exposure Affecting github.com/kubernetes-sigs/secrets-store-csi-driver/pkg/secrets-store package, versions <1.3.3


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.05% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Information Exposure vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-GOLANG-GITHUBCOMKUBERNETESSIGSSECRETSSTORECSIDRIVERPKGSECRETSSTORE-5660297
  • published28 May 2023
  • disclosed26 May 2023
  • creditTomer Shaiman from Microsoft.

Introduced: 26 May 2023

CVE-2023-2878  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade github.com/kubernetes-sigs/secrets-store-csi-driver/pkg/secrets-store to version 1.3.3 or higher.

Overview

Affected versions of this package are vulnerable to Information Exposure in secrets-store-csi-driver where an actor with access to the driver logs can observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions.

Note: Tokens are only logged when the TokenRequests is configured in the CSIDriver object and the driver is set to run at log level 2 or greater via the -v flag.

To check if token requests are configured, run the following command:

kubectl get csidriver secrets-store.csi.k8s.io -o jsonpath="{.spec.tokenRequests}"

To check if tokens are being logged, examine the secrets-store container log:

kubectl logs -l app=secrets-store-csi-driver -c secrets-store -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens"

References

CVSS Scores

version 3.1