dbcve.org
SplunkApplication

CVE-2024-45741

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-14
Fix available
A fix is available. Upgrade to 9.1.6 / 9.1.2312.205 or later.
See remediation →
58/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.3 and 9.1.6 and Splunk Cloud Platform versions below 9.2.2403.108 and 9.1.2312.205, a low-privileged user that does not hold the "admin" or "power" Splunk roles could create a malicious payload through a custom configuration file that the "api.uri" parameter from the "/manager/search/apps/local" endpoint in Splunk Web calls. This could result in execution of unauthorized JavaScript code in the browser of a user.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in Splunk Web. A low-privileged user (non-admin, non-power) can inject malicious JavaScript by crafting a payload through a custom configuration file that the 'api.uri' parameter at the /manager/search/apps/local endpoint processes. When other users access this endpoint, the malicious payload executes in their browsers.

MitigationUpgrade Splunk Enterprise to version 9.2.3 or 9.1.6 (or later), and Splunk Cloud Platform to 9.2.2403.108 or 9.1.2312.205 (or later) to patch the XSS vulnerability in the api.uri parameter processing.

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.1.0, < 9.1.6>= 9.2.0, < 9.2.3
Splunk Cloud PlatformApplication
Affected:>= 9.1.2312, < 9.1.2312.205>= 9.2.2403.100, < 9.2.2403.108

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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
    Run: splunk --version or access Settings > About in Splunk Web to view the version number
    Affected if The installed version is >= 9.1.0 and < 9.1.6, or >= 9.2.0 and < 9.2.3 (for Splunk Enterprise)
  2. Check Splunk Cloud Platform version
    Access the Splunk Cloud Portal or run: splunkd version in the management interface
    Affected if The installed version is >= 9.1.2312 and < 9.1.2312.205, or >= 9.2.2403.100 and < 9.2.2403.108 (for Splunk Cloud Platform)
  3. Verify Splunk Web interface is enabled
    Check $SPLUNK_HOME/etc/system/default/web.conf for the 'enableWebssl' or 'mgmtHostPort' settings, or verify the Splunk Web service is running
    Affected if Splunk Web is enabled and accessible (required for the vulnerable endpoint)
  4. Inspect custom app configurations for suspicious api.uri values
    Review local app configuration files in $SPLUNK_HOME/etc/apps/ and $SPLUNK_HOME/etc/users/ for entries containing 'api.uri' parameter, particularly in local.meta or app.conf files
    Affected if A custom app configuration contains a crafted api.uri parameter with malicious JavaScript payload
  5. Review access logs for the vulnerable endpoint
    Examine $SPLUNK_HOME/var/log/splunk/web_access.log for requests to /manager/search/apps/local with suspicious uri= parameters
    Affected if Requests from low-privileged users to the /manager/search/apps/local endpoint contain encoded XSS payloads in the uri parameter

A user is affected if they run a vulnerable Splunk version and have custom apps with malicious api.uri configurations accessible to low-privileged users via the Splunk Web manager 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.1.6 / 9.1.2312.205 / 9.2.3 or later
Fixed in 9.1.69.1.2312.2059.2.3
Interim mitigation

Upgrade Splunk Enterprise to version 9.2.3 or 9.1.6 (or later), and Splunk Cloud Platform to 9.2.2403.108 or 9.1.2312.205 (or later) to patch the XSS vulnerability in the api.uri parameter processing.

Recommended fix High confidence

Splunk Enterprise: 9.1.6 or 9.2.3; Splunk Cloud Platform: 9.1.2312.205 or 9.2.2403.108

  1. Identify your current Splunk version by navigating to Settings > About > Version information
  2. For Splunk Enterprise 9.1.x: Upgrade to version 9.1.6 or later
  3. For Splunk Enterprise 9.2.x: Upgrade to version 9.2.3 or later
  4. For Splunk Cloud Platform 9.1.x: Contact Splunk Support to request upgrade to version 9.1.2312.205 or later
  5. For Splunk Cloud Platform 9.2.x: Contact Splunk Support to request upgrade to version 9.2.2403.108 or later
  6. After upgrade, verify the fix by confirming the /manager/search/apps/local endpoint properly sanitizes the api.uri parameter
  7. Review Splunk release notes for any configuration changes in the new version
Caveat Review Splunk release notes for backward compatibility changes; test in non-production environment before upgrading production

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

Fix this in Splunk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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