dbcve.org
CloudApplication · Splunk

CVE-2024-36986

MEDIUM · 5.7 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 →
61/100
Remediation priority · Elevated
Remotely reachable

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.200 and 9.1.2308.207, an authenticated user could run risky commands using the permissions of a higher-privileged user to bypass SPL safeguards for risky commands in the Analytics Workspace. The vulnerability requires the authenticated user to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.

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

In Splunk Enterprise and Cloud Platform, an authenticated attacker exploits the Analytics Workspace to bypass SPL safeguards for risky commands. By tricking a higher-privileged user into initiating a request in their browser (phishing), the attacker can execute risky commands with the victim's elevated permissions.

MitigationUpgrade Splunk Enterprise to versions 9.2.2, 9.1.5, or 9.0.10 (and later), or upgrade Splunk Cloud Platform to versions 9.1.2312.200, 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, < 9.1.2312.200
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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check Splunk Enterprise version
    Navigate to Settings > About > Version or run: splunk --version
    Affected if Version falls within 9.0.0 to 9.0.9, 9.1.0 to 9.1.4, or 9.2.0 to 9.2.1
  2. Check Splunk Cloud version
    Navigate to Settings > Account > License and Usage or check the cloud console for version information
    Affected if Version falls within 9.1.2308 to 9.1.2308.206 or 9.1.2312 to 9.1.2312.199
  3. Verify Analytics Workspace is enabled
    Navigate to Settings > Analytics > Analytics Workspace or check local/splunk_analytics_workspace.conf for enabled status
    Affected if Analytics Workspace feature is turned on in the configuration
  4. Inspect user roles and permissions
    Navigate to Settings > Users, Roles, and Authentication > Roles and review which roles have permissions to execute risky SPL commands
    Affected if Roles with elevated SPL command permissions exist alongside lower-privilege authenticated users who could exploit them

A user is affected if their Splunk version is within the vulnerable ranges AND Analytics Workspace is enabled, allowing an authenticated attacker to leverage higher-privileged user sessions.

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 versions 9.2.2, 9.1.5, or 9.0.10 (and later), or upgrade Splunk Cloud Platform to versions 9.1.2312.200, 9.1.2308.207, or later.

Recommended fix High confidence

Splunk Enterprise: 9.0.10, 9.1.5, or 9.2.2 | Splunk Cloud Platform: 9.1.2308.207 or 9.1.2312.200

  1. Identify your current Splunk Enterprise or Splunk Cloud Platform version from the About page
  2. For Splunk Enterprise: Upgrade to version 9.0.10, 9.1.5, or 9.2.2 (or later)
  3. For Splunk Cloud Platform: Upgrade to version 9.1.2308.207 or 9.1.2312.200 (or later)
  4. After upgrade, verify the Analytics Workspace SPL safeguards are functioning correctly
  5. Review user permissions and educate users about phishing risks as an additional defensive measure
Caveat Review Splunk upgrade documentation for potential compatibility issues with custom apps or configurations

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

Fix this in Cloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36986 — 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-36986 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