File overwrite via unsanitized archive entry paths
Published Jan 29, 2023 · Updated Aug 3, 2024
Path traversal in JSZip before 3.8.0 allows attackers to supply archive entries that escape an intended extraction directory. The loadAsync path in lib/load.js passed each raw fileNameStr to zip.file without resolving dot-dot components, leaving traversal names in the returned entry map. Exploitation requires consuming code to accept an untrusted ZIP and write entries using those names; resulting file access is bounded by that process's permissions.
Summary
What happened
Path traversal in JSZip before 3.8.0 allows attackers to supply archive entries that escape an intended extraction directory. The loadAsync path in lib/load.js passed each raw fileNameStr to zip.file without resolving dot-dot components, leaving traversal names in the returned entry map. Exploitation requires consuming code to accept an untrusted ZIP and write entries using those names; resulting file access is bounded by that process's permissions.
The record
- CVE
- CVE-2022-48285
- Published
- Jan 29, 2023
- Updated
- Aug 3, 2024
- Vendor
- JSZip Project
- Product
- JSZip
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <3.8.0
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.
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