dbcve.org
CloudApplication · Splunk

CVE-2024-36982

HIGH · 7.5 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 9.0.10 / 9.1.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A null pointer reference vulnerability exists in Splunk Enterprise and Cloud Platform REST API endpoints. An attacker can trigger a null pointer dereference by sending a specially crafted request to the cluster/config endpoint, causing the Splunk daemon to crash and resulting in denial of service.

MitigationUpgrade Splunk Enterprise to version 9.2.2, 9.1.5, or 9.0.10 or later; upgrade Splunk Cloud Platform to version 9.1.2312.109 or 9.1.2308.207 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CloudApplication
Affected:>= 9.1.2308, < 9.1.2308.207>= 9.1.2312.100, < 9.1.2312.109
SplunkApplication
Affected:>= 9.0.0, < 9.0.10>= 9.1.0, < 9.1.5>= 9.2.0, < 9.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Splunk Enterprise version
    Run 'splunk --version' from the Splunk installation bin directory, or check the version displayed on the Splunk Web login page, or examine the $SPLUNK_HOME/etc/splunk.version file
    Affected if The installed version falls within any of these ranges: 9.0.0 to 9.0.9, 9.1.0 to 9.1.4, 9.2.0 to 9.2.1
  2. Determine installed Splunk Cloud version
    Check the Splunk Cloud portal for the current platform version, or access the Splunk Web settings page showing the deployment version
    Affected if The installed version is 9.1.2308 through 9.1.2308.206, or 9.1.2312.100 through 9.1.2312.108
  3. Verify cluster/config endpoint accessibility
    Send an HTTP GET request to the /services/cluster/config endpoint (e.g., curl -k https://localhost:8089/services/cluster/config) using Splunk REST API credentials
    Affected if The endpoint is reachable and responds, indicating the REST API is enabled and the cluster configuration is accessible over the network

You are affected if your Splunk version is within the affected ranges AND the cluster/config REST API endpoint is accessible, since the null pointer dereference occurs when a crafted request is sent to that specific endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.10 / 9.1.5 / 9.1.2308.207 or later
Fixed in 9.0.109.1.59.1.2308.207
Interim mitigation

Upgrade Splunk Enterprise to version 9.2.2, 9.1.5, or 9.0.10 or later; upgrade Splunk Cloud Platform to version 9.1.2312.109 or 9.1.2308.207 or later.

Recommended fix High confidence

Splunk Enterprise: 9.0.10, 9.1.5, or 9.2.2 (or later) | Splunk Cloud Platform: 9.1.2308.207 or 9.1.2312.109 (or later)

  1. 1. Identify the current Splunk Enterprise or Splunk Cloud Platform version by checking the About page or running `splunk version`
  2. 2. For Splunk Enterprise: Plan the upgrade to version 9.0.10, 9.1.5, or 9.2.2 (or later) depending on your current major version branch
  3. 3. For Splunk Cloud Platform: Contact Splunk support to schedule the upgrade to version 9.1.2308.207 or 9.1.2312.109 (or later)
  4. 4. Before upgrading, perform a full backup of Splunk configuration and data directories
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade following Splunk's standard upgrade procedure
  7. 7. After upgrade, verify the Splunk daemon is running and accessible
  8. 8. Confirm the fix by checking that the /services/cluster/config endpoint no longer triggers a null pointer dereference

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36982 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data