Code execution via unsanitized cross-partition deserialization
Published Jan 22, 2024 · Updated Jun 17, 2025
Unsafe deserialization in Splunk Web in Splunk Enterprise for Windows 9.0.0 through 9.0.7 and 9.1.0 through 9.1.2 allows local users to execute code. Splunk Web fails to sanitize a path that reaches deserialization, allowing serialized data placed on a separate disk partition to be treated as trusted input. Exploitation requires low-privileged local access, a separate partition, and user interaction; successful exploitation executes code in a changed security scope.
Summary
What happened
Unsafe deserialization in Splunk Web in Splunk Enterprise for Windows 9.0.0 through 9.0.7 and 9.1.0 through 9.1.2 allows local users to execute code. Splunk Web fails to sanitize a path that reaches deserialization, allowing serialized data placed on a separate disk partition to be treated as trusted input. Exploitation requires low-privileged local access, a separate partition, and user interaction; successful exploitation executes code in a changed security scope.
The record
- CVE
- CVE-2024-23678
- Published
- Jan 22, 2024
- Updated
- Jun 17, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 22, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record 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=9.0 <9.0.8
- Affected versionversion=9.1 <9.1.3
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