CVE-2024-45733
Published: 14 October 2024
Summary
CVE-2024-45733 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Splunk Splunk. 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-45733 is an insecure session storage configuration vulnerability, tracked under CWE-502, that affects Splunk Enterprise for Windows in versions below 9.2.3 and 9.1.6. The flaw permits remote code execution with a CVSS 3.1 base score of 8.8.
A low-privileged user lacking the admin or power Splunk roles can exploit the issue over the network without user interaction to obtain full control over confidentiality, integrity, and availability on the affected system.
The Splunk advisory SVD-2024-1003 and associated research note recommend upgrading to the fixed releases 9.2.3 or 9.1.6 to eliminate the insecure session storage path.
EPSS scores have remained low, reaching a peak of 0.0692 before receding to the current value of 0.0406, with no reported real-world exploitation activity.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-41737
Vulnerability details
In Splunk Enterprise for Windows versions below 9.2.3 and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could perform a Remote Code Execution (RCE) due to an insecure session storage configuration.
- 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.