CVE-2024-53247
Published: 10 December 2024
Summary
CVE-2024-53247 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 11.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2024-53247 is a deserialization of untrusted data flaw (CWE-502) affecting Splunk Enterprise versions below 9.3.2, 9.2.4, and 9.1.7, along with Splunk Secure Gateway app versions below 3.4.261 and 3.7.13 on Splunk Cloud Platform. The vulnerability carries a CVSS score of 8.8 and permits remote code execution.
A low-privileged user lacking the admin or power Splunk roles can exploit the issue over the network without user interaction, resulting in full compromise of confidentiality, integrity, and availability on the target system.
The referenced Splunk advisory SVD-2024-1205 addresses mitigation through version upgrades to the fixed releases. The associated EPSS score rose from lower values to a peak of 0.0576 after disclosure before receding to the current 0.0410.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-51919
Vulnerability details
In Splunk Enterprise versions below 9.3.2, 9.2.4, and 9.1.7, and versions below 3.4.261 and 3.7.13 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could perform…
more
a Remote Code Execution (RCE).
- 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.