dbcve.org
SplunkApplication

CVE-2024-45731

HIGH · 8.0 CVSS v3.1 Published 2024-10-14
Fix available
A fix is available. Upgrade to 9.1.6 / 9.2.3 or later.
See remediation →
84/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 for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could write a file to the Windows system root directory, which has a default location in the Windows System32 folder, when Splunk Enterprise for Windows is installed on a separate drive.

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 path traversal vulnerability in Splunk Enterprise for Windows allows a low-privileged user (non-admin/non-power role) to write files to the Windows system root directory (System32 folder) when Splunk is installed on a separate drive. This enables privilege escalation by placing malicious files in a privileged system location.

MitigationUpgrade Splunk Enterprise for Windows to version 9.3.1, 9.2.3, or 9.1.6 or later to patch this vulnerability. Alternatively, restrict filesystem permissions for low-privileged Splunk users to prevent write access to system directories.

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= 9.3.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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. Identify Splunk Enterprise version
    Check the installed Splunk version by examining the version file in the Splunk installation directory, or run 'splunk --version' from the Splunk bin directory
    Affected if The installed version falls within >= 9.1.0 and < 9.1.6, OR >= 9.2.0 and < 9.2.3, OR equals 9.3.0
  2. Confirm Windows platform
    Verify that Splunk Enterprise is running on a Windows operating system
    Affected if Splunk is running on Windows (the vulnerability only affects Windows installations)
  3. Determine Splunk installation drive
    Check which drive letter Splunk is installed on by reviewing the installation path
    Affected if Splunk is installed on a drive other than the default Windows system drive (the vulnerability only applies when Splunk is on a separate drive)
  4. Identify low-privileged Splunk users
    Review Splunk user roles and Windows filesystem permissions for the Splunk installation directory to identify non-admin/non-power role users
    Affected if Low-privileged Splunk users exist with write access to Splunk directories that can be traversed to system locations

You are affected if Splunk Enterprise for Windows is running a version between 9.1.0-9.1.5, 9.2.0-9.2.2, or 9.3.0 AND is installed on a separate drive from the Windows system, allowing low-privileged users potential write access to privileged system locations.

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.2.3 or later
Fixed in 9.1.69.2.3
Interim mitigation

Upgrade Splunk Enterprise for Windows to version 9.3.1, 9.2.3, or 9.1.6 or later to patch this vulnerability. Alternatively, restrict filesystem permissions for low-privileged Splunk users to prevent write access to system directories.

Recommended fix High confidence

Minimum: 9.1.6, 9.2.3, or 9.3.1 (depending on current branch)

  1. 1. Identify the current Splunk Enterprise for Windows version by navigating to Settings > About > About Splunk Enterprise
  2. 2. Based on current version, upgrade to the minimum fixed release: For 9.1.x branch, upgrade to 9.1.6 or later; For 9.2.x branch, upgrade to 9.2.3 or later; For 9.3.0, upgrade to 9.3.1 or later
  3. 3. Download the appropriate installer from splunk.com/products/splunk/downloads
  4. 4. Stop the Splunk Enterprise service before upgrading: Run 'splunk stop' from the Splunk bin directory
  5. 5. Run the installer with appropriate administrator privileges
  6. 6. Start Splunk Enterprise after upgrade completes: Run 'splunk start' from the Splunk bin directory
  7. 7. Verify the upgrade by checking the version in Settings > About > About Splunk Enterprise
Caveat Standard minor version upgrade risks apply; review Splunk upgrade documentation for pre-upgrade backup requirements

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

Fix this in Splunk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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