Arbitrary file relocation via unsanitized rename path
Published Jul 28, 2021 · Updated Sep 16, 2024
Path traversal in mguinness elFinder.AspNet before 1.1.1 allows remote attackers to relocate files outside the configured volume. FileSystemDriver.RenameAsync combines a user-controlled name with the parent path and passes the result to File.Move or Directory.Move without first verifying that the resolved path remains under the volume root. An exposed connector endpoint is sufficient; parent-directory segments can move an existing file or directory beyond the application's intended storage boundary.
Summary
What happened
Path traversal in mguinness elFinder.AspNet before 1.1.1 allows remote attackers to relocate files outside the configured volume. FileSystemDriver.RenameAsync combines a user-controlled name with the parent path and passes the result to File.Move or Directory.Move without first verifying that the resolved path remains under the volume root. An exposed connector endpoint is sufficient; parent-directory segments can move an existing file or directory beyond the application's intended storage boundary.
The record
- CVE
- CVE-2021-23415
- Published
- Jul 28, 2021
- Updated
- Sep 16, 2024
- Vendor
- mguinness
- Product
- elFinder.AspNet
- Classifications
- CWE-22, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <1.1.1
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
- Snyk rename-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