Out-of-directory file writes via symlinked archive parents
Published Feb 5, 2021 · Updated Aug 4, 2024
Path traversal in GNOME gnome-autoar 0.2.4 and earlier allows remote attackers to write files outside the extraction directory. autoar-extractor.c fails to reject an archive entry whose parent is a symbolic link to a directory outside the extraction root. Exploitation requires a user to extract a crafted archive and can overwrite files writable by the extracting process.
Summary
What happened
Path traversal in GNOME gnome-autoar 0.2.4 and earlier allows remote attackers to write files outside the extraction directory. autoar-extractor.c fails to reject an archive entry whose parent is a symbolic link to a directory outside the extraction root. Exploitation requires a user to extract a crafted archive and can overwrite files writable by the extracting process.
The record
- CVE
- CVE-2020-36241
- Published
- Feb 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, CWE-22, T1204.002, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 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
- GNOME issue 7 malicious archive reproducerproof 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