Arbitrary file access via chained symbolic links
Published May 14, 2024 · Updated Aug 4, 2024
Path traversal in Dotmesh 0 through 0.8.1 allows remote authenticated users to read or write files via a crafted tar archive. The untarFile routine validates each relative link target in isolation, so two accepted parent links resolve beyond the extraction root. Control of an archive is required; writes inherit the unpacking process's permissions, while reads also require access to extracted files.
Summary
What happened
Path traversal in Dotmesh 0 through 0.8.1 allows remote authenticated users to read or write files via a crafted tar archive. The untarFile routine validates each relative link target in isolation, so two accepted parent links resolve beyond the extraction root. Control of an archive is required; writes inherit the unpacking process's permissions, while reads also require access to extracted files.
The record
- CVE
- CVE-2020-26312
- Published
- May 14, 2024
- Updated
- Aug 4, 2024
- Vendor
- Subtree
- Product
- Dotmesh
- Classifications
- CWE-125, CWE-787
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2024CVE 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=0 <=0.8.1
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- GHSL chained-symbolic-link 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