dbcve.org
SplunkApplication

CVE-2024-45733

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 for Windows versions below 9.2.3 and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could perform a Remote Code Execution (RCE) due to an insecure session storage configuration.

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

Splunk Enterprise for Windows versions below 9.2.3 and 9.1.6 contains an insecure session storage configuration that allows low-privileged users (non-admin, non-power roles) to manipulate session data and achieve remote code execution on the underlying Windows system.

MitigationUpgrade to Splunk Enterprise 9.2.3, 9.1.6, or later. Alternatively, restrict filesystem permissions on Splunk directories and review role-based access controls to limit low-privileged users from modifying session storage.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Splunk Enterprise version on Windows
    Open a command prompt and navigate to the Splunk bin directory (typically C:\Program Files\Splunk\bin), then run: splunk --version or check the Windows Registry under HKLM\SOFTWARE\Splunk\Splunk\Version
    Affected if The installed version is 9.1.0 through 9.1.5, or 9.2.0 through 9.2.2 (versions below 9.1.6 or 9.2.3)
  2. Locate session storage configuration files
    Check Splunk web configuration files (web.conf) in the Splunk etc/system/local/ or etc/apps/search/local/ directories for session storage settings
    Affected if Session storage is configured to use insecure file-based storage rather than a secure session manager, or session files are stored in a world-writable location
  3. Inspect session file storage directory permissions
    Right-click the Splunk installation directory (typically C:\Program Files\Splunk), select Properties, go to the Security tab, and review write permissions for non-admin users; or use icacls from command line: icacls 'C:\Program Files\Splunk'
    Affected if Low-privileged users (non-admin, non-power roles) have write access to directories where session files are stored
  4. Check Splunk role-based access control configuration
    Open Splunk Web, navigate to Settings > Users and Authentication > Roles, or inspect authorization.conf in the Splunk etc/system/local/ directory
    Affected if Roles assigned to low-privileged users grant them permissions that can be combined with session file manipulation to achieve code execution

A user is affected if they are running Splunk Enterprise for Windows at a version below 9.1.6 or 9.2.3 AND low-privileged users have write access to session storage 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 to Splunk Enterprise 9.2.3, 9.1.6, or later. Alternatively, restrict filesystem permissions on Splunk directories and review role-based access controls to limit low-privileged users from modifying session storage.

Recommended fix High confidence

Upgrade to Splunk Enterprise 9.1.6, 9.2.3, or later

  1. Identify the current Splunk Enterprise version by navigating to Settings > About > Version or running 'splunk --version' in CLI
  2. Download Splunk Enterprise version 9.1.6 or 9.2.3 (or later) from splunk.com
  3. Review Splunk documentation for upgrade procedures: https://docs.splunk.com/Documentation/Splunk/latest/Installation/UpgradeSplunk
  4. Create a full backup of your Splunk environment including $SPLUNK_HOME and configuration files
  5. Test the upgrade in a non-production environment first
  6. Stop the Splunk service: splunk stop
  7. Run the installer for the new version on Windows
  8. Start the Splunk service: splunk start
Caveat Standard Splunk upgrade considerations apply - review release notes for any breaking changes between your current version and target version, especially regarding custom apps and configurations

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

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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