Arbitrary file write via tar path traversal
Published Jun 16, 2020 · Updated Aug 4, 2024
Path traversal in Helm 3.0.0 through 3.2.3 allows remote authenticated users to write files outside the plugin directory via a malicious HTTP tar archive. The HTTP plugin extractor joined archive entry names directly to the destination path, so relative or absolute names escaped the intended directory; the patch adds path and symlink checks. Exploitation requires a Helm user to install the attacker-controlled plugin, enabling overwrite of accessible files and potential subsequent code execution.
Summary
What happened
Path traversal in Helm 3.0.0 through 3.2.3 allows remote authenticated users to write files outside the plugin directory via a malicious HTTP tar archive. The HTTP plugin extractor joined archive entry names directly to the destination path, so relative or absolute names escaped the intended directory; the patch adds path and symlink checks. Exploitation requires a Helm user to install the attacker-controlled plugin, enabling overwrite of accessible files and potential subsequent code execution.
The record
- CVE
- CVE-2020-4053
- Published
- Jun 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Helm Project
- Product
- Helm
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.0.0, < 3.2.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo