Unauthenticated file write via ZIP path traversal
Published Oct 18, 2024 · Updated Oct 18, 2024
Unrestricted file upload in wfh45678 Radar 1.0.8 and earlier allows remote attackers to write files via the common upload API. The /services/v1/common/upload endpoint passes a multipart ZIP filename to ZipUtils.unZipIt without filtering ../ path segments. No authentication is required; a crafted filename escapes the intended D://radar directory during decompression, allowing attacker-chosen file placement.
Summary
What happened
Unrestricted file upload in wfh45678 Radar 1.0.8 and earlier allows remote attackers to write files via the common upload API. The /services/v1/common/upload endpoint passes a multipart ZIP filename to ZipUtils.unZipIt without filtering ../ path segments. No authentication is required; a crafted filename escapes the intended D://radar directory during decompression, allowing attacker-chosen file placement.
The record
- CVE
- CVE-2024-10120
- Published
- Oct 18, 2024
- Updated
- Oct 18, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 18, 2024CVE publishedPublication date reported by the CVE source.
- Oct 18, 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
- Radar arbitrary file upload 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