Arbitrary file write via unsanitized archive paths
Published Aug 8, 2021 · Updated Aug 4, 2024
Path traversal in gen2brain go-unarr before 0.1.4 allows attackers to write files outside the extraction directory using a crafted TAR archive. Archive.Name returned unarrc.EntryGetName directly, leaving absolute and ../ components in attacker-controlled entry names. Exploitation requires a consuming application or user to extract the crafted archive; writes occur with the extractor's filesystem permissions.
Summary
What happened
Path traversal in gen2brain go-unarr before 0.1.4 allows attackers to write files outside the extraction directory using a crafted TAR archive. Archive.Name returned unarrc.EntryGetName directly, leaving absolute and ../ components in attacker-controlled entry names. Exploitation requires a consuming application or user to extract the crafted archive; writes occur with the extractor's filesystem permissions.
The record
- CVE
- CVE-2021-38197
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2021CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Upstream malicious archive demonstrationproof of concept · demonstrated
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