Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Kubernetes secrets-store-csi-driver discloses service account tokens in logs

CVSS 3.1 6.5 MEDIUMEUVD CVSS 3.1 6.5 CVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS 3.1 · [email protected] · Primary 5.5 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by sigs.k8s.io/secrets-store-csi-driver 1.3.3osv · severity unknownFixed by sigs.k8s.io/secrets-store-csi-driver 1.3.3KEV status unknown

cve-program · CVE-2023-2878

Published

Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs.

Read the publisher's advisory

euvd · EUVD-2023-1539

Published

Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs.

Read the publisher's advisory

nvd · CVE-2023-2878

Published

Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs.

Read the publisher's advisory

osv · GHSA-g82w-58jf-gcxx

Published

A security issue was discovered in secrets-store-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](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag. This issue has been rated MEDIUM [CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) (6.5), and assigned CVE-2023-2878 ### Am I vulnerable? You may be vulnerable if [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) 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: ```bash 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: ```bash kubectl logs -l app=secrets-store-csi-driver -c secrets-store -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens" ``` ### Affected Versions - secrets-store-csi-driver < 1.3.3 ### How do I mitigate this vulnerability? Prior to upgrading, this vulnerability can be mitigated by running secrets-store-csi-driver at log level 0 or 1 via the -v flag. ### Fixed Versions - secrets-store-csi-driver >= 1.3.3 To upgrade, refer to the documentation: https://secrets-store-csi-driver.sigs.k8s.io/getting-started/upgrades.html#upgrades ### 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]](https://groups.google.com/)

Read the publisher's advisory

osv · GO-2023-1793

Published

secrets-store-csi-driver discloses service account tokens in logs in sigs.k8s.io/secrets-store-csi-driver

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2023-2878 · CVE overview and exploitation status

EUVD-2023-1539

GHSA-g82w-58jf-gcxx

GO-2023-1793

cve-program · CVE-2023-2878

euvd · EUVD-2023-1539

nvd · CVE-2023-2878

osv · GHSA-g82w-58jf-gcxx

osv · GO-2023-1793

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 13:23 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current