← Back
CVE-2020-8567
Path Traversal in github.com/hashicorp/vault-csi-provider (CVE-2020-8567)
Summary
path traversal in github.com/hashicorp/vault-csi-provider (CVE-2020-8567). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.2.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2020-8567** has been found in github.com/hashicorp/vault-csi-provider.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/hashicorp/vault-csi-provider to **0.2.0** or later.
If unsure, ask your IT team or search "github.com/hashicorp/vault-csi-provider CVE-2020-8567" on the vendor's site.
CVE-2020-8567 (github.com/hashicorp/vault-csi-provider) — CWE-22 /
Attack vector: remote (network-reachable) / no user interaction
Patched: `0.2.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in github.com/hashicorp/vault-csi-provider.
📍 Affected scope
github.com/hashicorp/vault-csi-provider — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.2.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/hashicorp/vault-csi-provider' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/hashicorp/vault-csi-provider' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/hashicorp/vault-csi-provider` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/hashicorp/vault-csi-provider to 0.2.0ステージング環境で 0.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/hashicorp/vault-csi-provider
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go
github.com/Azure/secrets-store-csi-driver-provider-azure
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go
github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.2.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2020-8567
- advisory https://github.com/advisories/GHSA-2v35-wj4r-rcmv
- patch https://github.com/Azure/secrets-store-csi-driver-provider-azure/pull/298
- patch https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp/pull/74
- web https://github.com/kubernetes-sigs/secrets-store-csi-driver/issues/384
- web https://github.com/hashicorp/secrets-store-csi-driver-provider-vault/pull/50
- web https://groups.google.com/g/kubernetes-secrets-store-csi-driver/c/BI2qisiNXHY