Arbitrary file write via chunk sanitization bypass
Published Oct 11, 2021 · Updated Aug 4, 2024
Path traversal in ProjectSend r1295 allows remote authenticated users with the Uploader role to write files outside the upload directory. In includes/upload.process.php, setting chunks to 2 skips fileName sanitization, allowing a name containing ../ sequences to control the .part file path. Uploader access and a crafted multipart upload are required; the demonstrated result places attacker-controlled content in the web root.
Summary
What happened
Path traversal in ProjectSend r1295 allows remote authenticated users with the Uploader role to write files outside the upload directory. In includes/upload.process.php, setting chunks to 2 skips fileName sanitization, allowing a name containing ../ sequences to control the .part file path. Uploader access and a crafted multipart upload are required; the demonstrated result places attacker-controlled content in the web root.
The record
- CVE
- CVE-2021-40886
- Published
- Oct 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 11, 2021CVE 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
- ProjectSend upload path traversal 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