Arbitrary file write via unchecked tar path
Published Jan 21, 2025 · Updated Feb 12, 2025
Path traversal in HashiCorp go-slug before 0.16.3 allows remote attackers to write arbitrary files through crafted tar entries. During extraction, the unpacker uses header.Name as the destination path and insufficiently validates a nonexistent attacker-supplied path against the extraction root. Exploitation requires a consuming application to extract an attacker-controlled Terraform-compatible slug; writes carry the application's filesystem permissions.
Summary
What happened
Path traversal in HashiCorp go-slug before 0.16.3 allows remote attackers to write arbitrary files through crafted tar entries. During extraction, the unpacker uses header.Name as the destination path and insufficiently validates a nonexistent attacker-supplied path against the extraction root. Exploitation requires a consuming application to extract an attacker-controlled Terraform-compatible slug; writes carry the application's filesystem permissions.
The record
- CVE
- CVE-2025-0377
- Published
- Jan 21, 2025
- Updated
- Feb 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, CAPEC-132, CAPEC-76, CAPEC-17, CAPEC-35
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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