Unauthenticated code execution via unsafe PHP deserialization
Published Jan 13, 2021 · Updated Aug 4, 2024
Unsafe deserialization in ThinkAdmin 4.0 through 6.0 allows remote attackers to execute arbitrary code through crafted POST data. The Update.php controller passes the rules and ignore POST values directly to PHP unserialize(), while Push.php does the same with receive, allowing attacker-controlled objects to be instantiated. No authentication or user interaction is required, and successful exploitation runs code in the web application's server context.
Summary
What happened
Unsafe deserialization in ThinkAdmin 4.0 through 6.0 allows remote attackers to execute arbitrary code through crafted POST data. The Update.php controller passes the rules and ignore POST values directly to PHP unserialize(), while Push.php does the same with receive, allowing attacker-controlled objects to be instantiated. No authentication or user interaction is required, and successful exploitation runs code in the web application's server context.
The record
- CVE
- CVE-2020-23653
- Published
- Jan 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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