Skip to content
Fencer Intel
medium 4.9

CVE-2020-8567 json

Kubernetes Secrets Store CSI Driver plugin directory traversals

published 5y ago modified last mo. also GHSA-2v35-wj4r-rcmv , GO-2024-2750 , EUVD-2022-2051

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.

Patch / fix

  • go github.com/hashicorp/vault-csi-provider 0.0.6
  • go github.com/Azure/secrets-store-csi-driver-provider-azure 0.0.10
  • go github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp 0.2.0
  • Kubernetes Kubernetes Secrets Store CSI Driver v0.0.6, v0.0.10, v0.2.0

Is CVE-2020-8567 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.1 4.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault-csi-provider
<0.0.6
all versions
0.0.6
go github.com/Azure/secrets-store-csi-driver-provider-azure
<0.0.10
all versions
0.0.10
go github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
<0.2.0
0.2.0

Affected products

  • Kubernetes Kubernetes Secrets Store CSI Driver

Classification

Weakness
  • CWE-24 Path Traversal: '../filedir'
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.