CMS data reset via install.lock deletion
Published Mar 21, 2022 · Updated Aug 3, 2024
Arbitrary file deletion in idcCMS 1.10 allows remote attackers to delete install.lock, resetting CMS settings and data. The public record identifies install.lock as the deletion target but does not disclose the request handler or code path that permits its removal. No authentication or user interaction is required; the documented consequence is an integrity loss through a CMS settings and data reset.
Summary
What happened
Arbitrary file deletion in idcCMS 1.10 allows remote attackers to delete install.lock, resetting CMS settings and data. The public record identifies install.lock as the deletion target but does not disclose the request handler or code path that permits its removal. No authentication or user interaction is required; the documented consequence is an integrity loss through a CMS settings and data reset.
The record
- CVE
- CVE-2022-27333
- Published
- Mar 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 21, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
No public exploit references are available in this record.
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