Unauthenticated arbitrary file write via path traversal
Published Apr 7, 2020 · Updated Aug 4, 2024
Path traversal in /servlet.gupld in LogicalDOC before 8.3.3 allows remote attackers to write files outside the upload directory. The servlet accepts ../ sequences in the multipart form-data name parameter and uses the resulting path without restricting it to the upload directory. No authentication or user interaction is required, and the demonstrated consequence is an arbitrary server-side file write.
Summary
What happened
Path traversal in /servlet.gupld in LogicalDOC before 8.3.3 allows remote attackers to write files outside the upload directory. The servlet accepts ../ sequences in the multipart form-data name parameter and uses the resulting path without restricting it to the upload directory. No authentication or user interaction is required, and the demonstrated consequence is an arbitrary server-side file write.
The record
- CVE
- CVE-2020-10366
- Published
- Apr 7, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- LogicalDOC multipart upload path-traversal proof of conceptfunctional · 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