Unauthenticated file deletion via path and extension parameters
Published Aug 20, 2021 · Updated Aug 4, 2024
Arbitrary file deletion in rConfig 3.9.5 allows remote attackers to delete files of a chosen extension via a crafted HTTP request. The ajaxDeleteAllLoggingFiles.php handler accepts attacker-controlled path and ext parameters and deletes every matching file without an authorization check. No authentication is required, and deletion of application or system files can corrupt stored data or interrupt the service.
Summary
What happened
Arbitrary file deletion in rConfig 3.9.5 allows remote attackers to delete files of a chosen extension via a crafted HTTP request. The ajaxDeleteAllLoggingFiles.php handler accepts attacker-controlled path and ext parameters and deletes every matching file without an authorization check. No authentication is required, and deletion of application or system files can corrupt stored data or interrupt the service.
The record
- CVE
- CVE-2020-25359
- Published
- Aug 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 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.
Public exploit references
- Stark0de rConfig arbitrary file deletion 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