Daemon crash via cluster/config null pointer dereference
Published Jul 1, 2024 · Updated Feb 28, 2025
Null pointer dereference in the REST API of Splunk Enterprise and Splunk Cloud Platform allows remote attackers to crash the Splunk daemon. A request to the cluster/config endpoint causes the handler to dereference a null pointer instead of rejecting the invalid state. The endpoint is network-reachable without prior authentication, and successful exploitation interrupts the affected Splunk service without exposing or modifying data.
Summary
What happened
Null pointer dereference in the REST API of Splunk Enterprise and Splunk Cloud Platform allows remote attackers to crash the Splunk daemon. A request to the cluster/config endpoint causes the handler to dereference a null pointer instead of rejecting the invalid state. The endpoint is network-reachable without prior authentication, and successful exploitation interrupts the affected Splunk service without exposing or modifying data.
The record
- CVE
- CVE-2024-36982
- Published
- Jul 1, 2024
- Updated
- Feb 28, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Feb 28, 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.10
- Affected versionversion=9.1 <9.1.5
- Affected versionversion=9.2 <9.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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