CVE-2025-29787: zip Vulnerable to Incorrect Path Canonicalization During Archive Extraction, Leading to Arbitrary File Write
First published: Mon Mar 17 2025(Updated: )
### Summary In the archive extraction routine of affected versions of the `zip` crate, symbolic links earlier in the archive are allowed to be used for later files in the archive without validation of the final canonicalized path, allowing maliciously crafted archives to overwrite arbitrary files in the file system when extracted. ### Details This is a variant of the [zip-slip](https://github.com/snyk/zip-slip-vulnerability) vulnerability, we can make the extraction logic step outside of the target directory by creating a symlink to the parent directory and then extracting further files through that symlink. The documentation of the [`::zip::read::ZipArchive::extract`] method is in my opinion implying this should not happen: > "Paths are sanitized with ZipFile::enclosed_name." ... > [`::zip::read::FileOptions::enclosed_name`] ... is resistant to path-based exploits ... can’t resolve to a path outside the current directory. Most archive software either decline to extract symlinks that traverse out of the directory or defer creation of symlinks after all files have been created to prevent unexpected behavior when later entries depend on earlier symbolic link entries. ### PoC https://gist.github.com/eternal-flame-AD/bf71ef4f6828e741eb12ce7fd47b7b85 ### Impact Users who extract untrusted archive files using the following high-level API method may be affected and critical files on the system may be overwritten with arbitrary file permissions, which can potentially lead to code execution. - zip::unstable::stream::ZipStreamReader::extract - zip::read::ZipArchive::extract
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Rust | >=1.3.0<2.3.0 | |
| rust/zip | >=1.3.0<2.3.0 | 2.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/zip-rs/zip2/security/advisories/GHSA-94vh-gphv-8pm8
- https://github.com/zip-rs/zip2/commit/a2e062f37066c3b12860a32eb1cb44856cfb7afe
- https://gist.github.com/eternal-flame-AD/bf71ef4f6828e741eb12ce7fd47b7b85
- https://github.com/zip-rs/zip2/releases/tag/v2.3.0
- https://nvd.nist.gov/vuln/detail/CVE-2025-29787
- https://github.com/advisories/GHSA-94vh-gphv-8pm8 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2025-29787?
CVE-2025-29787 has been classified as high severity due to its potential exploitation risks.
How do I fix CVE-2025-29787?
To fix CVE-2025-29787, upgrade the `zip` crate to version 2.3.0 or later.
What versions of the `zip` crate are affected by CVE-2025-29787?
CVE-2025-29787 affects `zip` crate versions starting from 1.3.0 up to, but not including, 2.3.0.
What impact does CVE-2025-29787 have on systems?
CVE-2025-29787 can lead to unauthorized access to files through symbolic link exploitation.
Is there a workaround for CVE-2025-29787 before upgrading?
There are no known effective workarounds for CVE-2025-29787 besides upgrading to a secure version.
- agent/weakness
- agent/title
- agent/first-publish-date
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/references
- agent/softwarecombine
- agent/description
- collector/nvd-cve
- agent/source
- agent/last-modified-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-94vh-gphv-8pm8
- alias/CVE-2025-29787
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/event
- agent/epss
- collector/epss-latest
- source/FIRST
- collector/github-advisory
- vendor/rust-lang
- canonical/rust
- package-manager/rust