Arbitrary file deletion via PHAR deserialization
Published Sep 24, 2021 · Updated Aug 4, 2024
PHAR deserialization in Concrete CMS 8.5.5 and earlier allows remote attackers to delete arbitrary files through a crafted path. The affected path check passes attacker-controlled phar:// input to is_dir, which deserializes PHAR metadata and invokes an object's __wakeup method. No authentication or user interaction is required, and deletion can compromise site integrity or interrupt service when application files are targeted.
Summary
What happened
PHAR deserialization in Concrete CMS 8.5.5 and earlier allows remote attackers to delete arbitrary files through a crafted path. The affected path check passes attacker-controlled phar:// input to is_dir, which deserializes PHAR metadata and invokes an object's __wakeup method. No authentication or user interaction is required, and deletion can compromise site integrity or interrupt service when application files are targeted.
The record
- CVE
- CVE-2021-40102
- Published
- Sep 24, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 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
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