Arbitrary file write via unsanitized ZIP paths
Published Dec 11, 2024 · Updated Dec 12, 2024
Path traversal in python-libarchive 4.2.1 and earlier allows attackers to write files outside the extraction directory via crafted ZIP entries. ZipFile.extract and extractall pass each unsanitized archive entry name to os.path.join, so an absolute or traversal path escapes the requested destination. Exploitation requires an application to extract an attacker-controlled ZIP archive, and resulting writes carry the permissions of that application process.
Summary
What happened
Path traversal in python-libarchive 4.2.1 and earlier allows attackers to write files outside the extraction directory via crafted ZIP entries. ZipFile.extract and extractall pass each unsanitized archive entry name to os.path.join, so an absolute or traversal path escapes the requested destination. Exploitation requires an application to extract an attacker-controlled ZIP archive, and resulting writes carry the permissions of that application process.
The record
- CVE
- CVE-2024-55587
- Published
- Dec 11, 2024
- Updated
- Dec 12, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- Dec 12, 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 directory traversal proof of conceptproof 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