CVE-2024-23052
Published: 29 February 2024
Summary
CVE-2024-23052 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in 5Kcrm Wukongcrm. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2024-23052 is a remote code execution vulnerability in WuKongOpenSource WukongCRM version 72crm_9.0.1_20191202. The flaw resides in the fastjson component's parseObject() function and is classified under CWE-502 (deserialization of untrusted data). It carries a CVSS 3.1 score of 9.8, reflecting network-accessible exploitation with no required credentials or user interaction.
An unauthenticated remote attacker can supply a malicious serialized object to the affected endpoint, triggering arbitrary code execution on the server. Successful exploitation grants full control over the application process, including the ability to read, modify, or delete data and potentially pivot within the environment.
Public references consist of GitHub repositories containing technical write-ups and issue reports that reproduce the flaw; no official vendor advisory or patch information is included in the available sources. The EPSS score stands at 0.7845 with an identical recorded peak, indicating sustained exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-20577
Vulnerability details
An issue in WuKongOpenSource WukongCRM v.72crm_9.0.1_20191202 allows a remote attacker to execute arbitrary code via the parseObject() function in the fastjson component.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
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.