dbcve.org
SplunkApplication

CVE-2024-36997

HIGH · 8.1 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 →
85/100
Remediation priority · High
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, an admin user could store and execute arbitrary JavaScript code in the browser context of another Splunk user through the conf-web/settings REST endpoint. This could potentially cause a persistent cross-site scripting (XSS) exploit.

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 · high confidence

A persistent XSS vulnerability in Splunk Enterprise (versions below 9.2.2, 9.1.5, and 9.0.10) and Splunk Cloud Platform (below 9.1.2312) allows an authenticated admin user to inject arbitrary JavaScript through the conf-web/settings REST endpoint. The malicious payload is stored and executes in the browser context of other Splunk users who access the affected content, enabling session hijacking, data theft, or further propagation.

MitigationUpgrade Splunk Enterprise to version 9.2.2, 9.1.5, or 9.0.10 (or higher), or upgrade Splunk Cloud Platform to version 9.1.2312 or later. Alternatively, restrict admin privileges and monitor the conf-web/settings endpoint for suspicious activity until patching is completed.

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
SplunkApplication
Affected:>= 9.0.0, < 9.0.10>= 9.1.0, < 9.1.5>= 9.2.0, < 9.2.2
Splunk Cloud PlatformApplication
Affected:>= 9.1.2312, < 9.1.2312.100

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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/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. Identify installed Splunk version
    Run the command: splunk --version or access the About page in Splunk Web (Settings > About) to view the exact version number
    Affected if The version is 9.0.0 to 9.0.9, 9.1.0 to 9.1.4, 9.2.0 to 9.2.1, or for Cloud Platform versions below 9.1.2312.100
  2. Review conf-web/settings endpoint access logs
    Search Splunk internal logs (index=_internal) for POST requests to services/conf-web/settings, looking for entries with unusual or suspicious values in the request body
    Affected if There are POST requests to conf-web/settings containing JavaScript tags, script src attributes, or encoded suspicious payloads that were successfully stored
  3. Inspect web configuration for stored XSS payloads
    Make a GET request to services/conf-web/settings or examine the contents of the web.conf file in $SPLUNK_HOME/etc/system/local/ for unexpected script tags or event handlers
    Affected if The configuration contains JavaScript code, script tags, img onerror attributes, or other XSS vectors in fields that should contain only plain text
  4. Check for unauthorized admin account modifications
    Review the authentication and authorization logs (index=_internal source=*authentication*) for any admin account changes or privilege escalations around the time of the conf-web/settings modification
    Affected if An authenticated admin user injected a malicious payload and that payload remains stored in the configuration

You are affected if your Splunk version falls within the vulnerable ranges AND there is evidence of a malicious payload stored in the conf-web/settings configuration 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.2312.100 or later
Fixed in 9.0.109.1.59.1.2312.100
Interim mitigation

Upgrade Splunk Enterprise to version 9.2.2, 9.1.5, or 9.0.10 (or higher), or upgrade Splunk Cloud Platform to version 9.1.2312 or later. Alternatively, restrict admin privileges and monitor the conf-web/settings endpoint for suspicious activity until patching is completed.

Recommended fix High confidence

Splunk Enterprise: 9.2.2 (or 9.1.5 or 9.0.10 minimum per your branch); Splunk Cloud Platform: 9.1.2312.100

  1. Identify your current Splunk Enterprise version by navigating to About > Version or running: splunk version
  2. For Splunk Enterprise 9.0.x: Upgrade to version 9.0.10 or later
  3. For Splunk Enterprise 9.1.x: Upgrade to version 9.1.5 or later
  4. For Splunk Enterprise 9.2.x: Upgrade to version 9.2.2 or later
  5. For Splunk Cloud Platform: Contact Splunk Support to request upgrade to 9.1.2312.100 or later
  6. After upgrade, verify the conf-web/settings endpoint no longer accepts unsanitized input
Caveat Review Splunk Upgrade Basics documentation before upgrading; test in non-production environment first; some forward compatibility considerations for custom apps and add-ons

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

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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