Application compromise via unsafe cache deserialization
Published May 6, 2022 · Updated Sep 16, 2024
Unsafe deserialization in ThinkPHP before 6.0.12 allows remote attackers to compromise application data through crafted cache input. The cache Driver sends nonnumeric cache values to its configured unserialize callback without validating whether serialized object data is trusted. Exploitation requires attacker-controlled data to reach an application's cache backend, with confidentiality and integrity loss and limited service interruption.
Summary
What happened
Unsafe deserialization in ThinkPHP before 6.0.12 allows remote attackers to compromise application data through crafted cache input. The cache Driver sends nonnumeric cache values to its configured unserialize callback without validating whether serialized object data is trusted. Exploitation requires attacker-controlled data to reach an application's cache backend, with confidentiality and integrity loss and limited service interruption.
The record
- CVE
- CVE-2021-23592
- Published
- May 6, 2022
- Updated
- Sep 16, 2024
- Vendor
- ThinkPHP
- Product
- ThinkPHP
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2022CVE 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 <6.0.12
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
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