Skip to content
Fencer Intel
high 7.5

CVE-2024-36982 json

Denial of Service through null pointer reference in “cluster/config” REST endpoint

published 2y ago modified 4mo ago also EUVD-2024-36370

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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.

Patch / fix

  • Splunk Splunk Enterprise 9.0.10, 9.1.5, 9.2.2
  • Splunk Splunk Cloud Platform 9.1.2308.207, 9.1.2312.109
  • splunk splunk_enterprise 9.0.10, 9.1.5, 9.2.2
  • splunk splunk_cloud_platform 9.1.2308.207, 9.1.2312.109

Is CVE-2024-36982 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Splunk Splunk Enterprise
  • Splunk Splunk Cloud Platform
  • splunk splunk_enterprise
  • splunk splunk_cloud_platform

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.