CVE-2024-44902
Published: 09 September 2024
Summary
CVE-2024-44902 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Thinkphp Thinkphp. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
A deserialization vulnerability tracked as CVE-2024-44902 affects ThinkPHP versions 6.1.3 through 8.0.4 and is associated with CWE-502. The flaw received a CVSS 3.1 score of 9.8, reflecting a network-accessible attack that requires no authentication or user interaction and can fully impact confidentiality, integrity, and availability.
An unauthenticated remote attacker can supply a malicious serialized payload to trigger arbitrary code execution on the target server. Successful exploitation grants the attacker the ability to run commands, access or modify data, and potentially take full control of the affected application instance.
The listed references include the ThinkPHP project site and a public GitHub repository containing exploit details for CVE-2024-44902. The EPSS score currently stands at 0.8367 with a recorded peak of 0.8412.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2779
Vulnerability details
A deserialization vulnerability in Thinkphp v6.1.3 to v8.0.4 allows attackers to execute arbitrary code.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Deserialization vulnerability in ThinkPHP web framework enables remote code execution on public-facing applications.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.