# CVE-2020-8567: Kubernetes Secrets Store CSI Driver plugin directory traversals > Attackers can write to arbitrary host files via crafted SecretProviderClass objects in Kubernetes Secrets Store CSI Driver plugins. - **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Jan 2021 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-2v35-wj4r-rcmv, GO-2024-2750 ## What is CVE-2020-8567? CVE-2020-8567 is a medium-severity path traversal vulnerability in Kubernetes Secrets Store CSI Driver, published on 21 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-24 (Path Traversal: '../filedir') ## Which versions are affected by CVE-2020-8567? 9 open source packages ship an affected version, including github.com/Azure/secrets-store-csi-driver-provider-azure, github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp and github.com/hashicorp/vault-csi-provider. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/Azure/secrets-store-csi-driver-provider-azure` | Go | All versions | None | | `github.com/Azure/secrets-store-csi-driver-provider-azure` | Go | All versions | 0.0.10 | | `github.com/Azure/secrets-store-csi-driver-provider-azure` | Go | All versions | 0.0.10 | | `github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp` | Go | All versions | 0.2.0 | | `github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp` | Go | All versions | 0.2.0 | | `github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp` | Go | All versions | 0.2.0 | | `github.com/hashicorp/vault-csi-provider` | Go | All versions | None | | `github.com/hashicorp/vault-csi-provider` | Go | All versions | 0.0.6 | | `github.com/hashicorp/vault-csi-provider` | Go | All versions | 0.0.6 | Products: Google Secret Manager Provider for Secret Store Csi Driver, Hashicorp Vault Provider for Secrets Store Csi Driver, Microsoft Azure Key Vault Provider for Secrets Store Csi Driver. ## How do I fix CVE-2020-8567? Upgrade github.com/Azure/secrets-store-csi-driver-provider-azure to 0.0.10 or later. ## Is CVE-2020-8567 being exploited? There is no known exploitation of CVE-2020-8567 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-8567 and fix it if it is affected. What it is: CVE-2020-8567 is a medium-severity path traversal vulnerability in Kubernetes Secrets Store CSI Driver, published on 21 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-8567 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/Azure/secrets-store-csi-driver-provider-azure (Go): affected all versions; no fix listed - github.com/Azure/secrets-store-csi-driver-provider-azure (Go): affected all versions; fixed in 0.0.10 - github.com/Azure/secrets-store-csi-driver-provider-azure (Go): affected all versions; fixed in 0.0.10 - github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp (Go): affected all versions; fixed in 0.2.0 - github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp (Go): affected all versions; fixed in 0.2.0 - github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp (Go): affected all versions; fixed in 0.2.0 - github.com/hashicorp/vault-csi-provider (Go): affected all versions; no fix listed - github.com/hashicorp/vault-csi-provider (Go): affected all versions; fixed in 0.0.6 - github.com/hashicorp/vault-csi-provider (Go): affected all versions; fixed in 0.0.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-8567/ (Markdown: https://insights.sbomify.com/CVE-2020-8567/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8567 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8567 - OSV: https://osv.dev/vulnerability/CVE-2020-8567 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-8567/ Summaries are generated and may contain mistakes; the official description above is the record.