Arbitrary file write via unchecked archive paths
Published Dec 17, 2022 · Updated Apr 15, 2025
Path traversal in LEMS jLEMS allows remote attackers to write files outside the extraction directory through a crafted JAR archive. The unpackJar function joins each untrusted JarEntry name to the output directory and writes it without first verifying that the normalized path remains inside that directory. A victim must cause the crafted archive to be processed; executable impact requires overwriting a security-sensitive file.
Summary
What happened
Path traversal in LEMS jLEMS allows remote attackers to write files outside the extraction directory through a crafted JAR archive. The unpackJar function joins each untrusted JarEntry name to the output directory and writes it without first verifying that the normalized path remains inside that directory. A victim must cause the crafted archive to be processed; executable impact requires overwriting a security-sensitive file.
The record
- CVE
- CVE-2022-4583
- Published
- Dec 17, 2022
- Updated
- Apr 15, 2025
- Vendor
- LEMS
- Product
- jLEMS
- Classifications
- CWE-22, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record 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=n/a
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
- jLEMS Zip Slip pull-request demonstrationproof 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