Arbitrary file write via Windows short-name traversal
Published Nov 4, 2024 · Updated Nov 21, 2024
Path traversal in Google safearchive before commit f7ce9d7 allows attackers to write arbitrary files during archive extraction. The tar Reader.Next and zip applyMagic paths sanitized archive names lexically but failed to reject Windows 8.3 short-name components that can resolve through symlink aliases. Exploitation requires a symlink-bearing archive to be extracted onto a case-insensitive filesystem that honors short names, and writes run with the extracting process's permissions.
Summary
What happened
Path traversal in Google safearchive before commit f7ce9d7 allows attackers to write arbitrary files during archive extraction. The tar Reader.Next and zip applyMagic paths sanitized archive names lexically but failed to reject Windows 8.3 short-name components that can resolve through symlink aliases. Exploitation requires a symlink-bearing archive to be extracted onto a case-insensitive filesystem that honors short names, and writes run with the extracting process's permissions.
The record
- CVE
- CVE-2024-10389
- Published
- Nov 4, 2024
- Updated
- Nov 21, 2024
- Vendor
- Product
- safearchive
- Classifications
- CWE-427, CWE-22, CAPEC-126
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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 <f7ce9d7b6f9c6ecd72d0b0f16216b046e55e44dc
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