Splunk Enterprise: NULL Pointer Dereference
CVE-2024-36982 is a high-severity NULL pointer dereference vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 9.2.2, 9.1.5, 9.0.10 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 9.2.2 or 9.1.5 or 9.0.10, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to 9.1.2312.109 or 9.1.2308.207, whichever matches your release line, or a later version.
- Update Cloud to 9.1.2308.207 or 9.1.2312.109, whichever matches your release line, or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 9.2 up to, but not including, 9.2.2; 9.1 up to, but not including, 9.1.5; 9.0 up to, but not including, 9.0.10 | 9.2.2, 9.1.5, 9.0.10 |
| Splunk | Splunk Cloud Platform | 9.1.2312 up to, but not including, 9.1.2312.109; 9.1.2308 up to, but not including, 9.1.2308.207 | 9.1.2312.109, 9.1.2308.207 |
| Splunk | Cloud | 9.1.2308 up to, but not including, 9.1.2308.207; 9.1.2312.100 up to, but not including, 9.1.2312.109 | 9.1.2308.207, 9.1.2312.109 |
| Splunk | Splunk | 9.0.0 up to, but not including, 9.0.10; 9.1.0 up to, but not including, 9.1.5; 9.2.0 up to, but not including, 9.2.2 | 9.0.10, 9.1.5, 9.2.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (splunk.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109 and 9.1.2308.207, an attacker could trigger a null pointer reference on the cluster/config REST endpoint, which could result in a crash of the Splunk daemon.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: NULL Pointer Dereference
The product dereferences a pointer that it expects to be valid but is NULL.
How developers prevent this class of flaw
- For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
- Select a programming language that is not susceptible to these issues.
- Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Recent NULL Pointer Dereference vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.