Path Traversal in helm.sh/helm/v3 (CVE-2020-4053)
Summary
Path traversal in helm.sh/helm/v3 (CVE-2020-4053). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.2.4 or later.
Original description
The description as published by the source.
The Helm core maintainers have identified an information disclosure
vulnerability in Helm 3.0.0-3.2.3.
Impact
A traversal attack is possible when installing Helm plugins from a tar
archive over HTTP. It is possible for a malicious plugin author to inject a relative
path into a plugin archive, and copy a file outside of the intended directory.
Traversal Attacks are a form of a Directory Traversal that can be exploited by
extracting files from an archive. The premise of the Directory Traversal
vulnerability is that an attacker can gain access to parts of the file system
outside of the target folder in which they should reside. The attacker can
then overwrite executable files and either invoke them remotely or wait for
the system or user to call them, thus achieving Remote Command Execution on
the victim's machine. The vulnerability can also cause damage by overwriting
configuration files or other sensitive resources, and can be exploited on both
client (user) machines and servers.
https://snyk.io/research/zip-slip-vulnerability
Specific Go Packages Affected
helm.sh/helm/v3/pkg/plugin/installer
Patches
This issue has been fixed in Helm 3.2.4
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Helm repository
- For security-specific issues, email us at cncf-helm-security@lists.cncf.io
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-4053 has been found in helm.sh/helm/v3.
Risk of unauthorized operations or information disclosure.
What to do: upgrade helm.sh/helm/v3 to 3.2.4 or later.
If unsure, ask your IT team or search "helm.sh/helm/v3 CVE-2020-4053" on the vendor's site.
CVE-2020-4053 (helm.sh/helm/v3) — CWE-22
Attack vector: remote (network-reachable)
Patched: 3.2.4 — 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.
Path traversal (CWE-22) exists in helm.sh/helm/v3.
Check the vendor advisory for the affected versions of helm.sh/helm/v3.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.2.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'helm.sh/helm/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'helm.sh/helm/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
helm.sh/helm/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade helm.sh/helm/v3 to 3.2.4ステージング環境で 3.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com