dbcve.org
SplunkApplication

CVE-2024-36991

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 on Windows versions below 9.2.2, 9.1.5, and 9.0.10, an attacker could perform a path traversal on the /modules/messaging/ endpoint in Splunk Enterprise on Windows. This vulnerability should only affect Splunk Enterprise on Windows.

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 exists in Splunk Enterprise on Windows in the /modules/messaging/ endpoint. Attackers can exploit this to access files outside the intended web root directory by manipulating path sequences in requests. This affects Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 on Windows only.

MitigationUpgrade Splunk Enterprise to version 9.2.2, 9.1.5, or 9.0.10 or later. If immediate patching is not possible, restrict access to the /modules/messaging/ endpoint via network controls or web application firewall rules.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Verify Splunk Enterprise is running on Windows
    Check the operating system where Splunk is installed. This vulnerability only affects Splunk Enterprise on Windows, not Linux or other platforms. Use 'systeminfo' or check the Splunk installation path (e.g., C:\Program Files\Splunk on Windows).
    Affected if The operating system is Windows and the other conditions below are met.
  2. Determine the installed Splunk Enterprise version
    Access Splunk Web, go to Settings > About > Version, or run the command: cd $SPLUNK_HOME && ./splunk --version (Linux) or cd %SPLUNK_HOME% && splunk.exe --version (Windows cmd).
    Affected if The version is 9.0.0 through 9.0.9, 9.1.0 through 9.1.4, or 9.2.0 through 9.2.1 (Windows only).
  3. Confirm the /modules/messaging/ endpoint is accessible
    Check if network or web application firewall rules allow access to the /modules/messaging/ endpoint. This endpoint must be reachable over HTTP/HTTPS for the path traversal to be exploitable.
    Affected if The /modules/messaging/ endpoint is exposed and reachable from a network position where an attacker could send malicious requests.

A user is affected if Splunk Enterprise is running on Windows, the installed version is within 9.0.0-9.0.9, 9.1.0-9.1.4, or 9.2.0-9.2.1, and the /modules/messaging/ endpoint is accessible.

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.2.2 or later
Fixed in 9.0.109.1.59.2.2
Interim mitigation

Upgrade Splunk Enterprise to version 9.2.2, 9.1.5, or 9.0.10 or later. If immediate patching is not possible, restrict access to the /modules/messaging/ endpoint via network controls or web application firewall rules.

Recommended fix High confidence

Upgrade to Splunk Enterprise 9.0.10, 9.1.5, or 9.2.2 (Windows)

  1. 1. Review Splunk Enterprise upgrade documentation at docs.splunk.com for your current version
  2. 2. Create a full backup of your Splunk Enterprise installation including $SPLUNK_HOME and configuration files
  3. 3. Download the appropriate Splunk Enterprise installer for Windows from splunk.com (version 9.0.10, 9.1.5, or 9.2.2)
  4. 4. Stop all Splunk Enterprise services on the Windows server
  5. 5. Run the installer and follow the upgrade wizard prompts
  6. 6. After installation, verify the Splunk Enterprise services start successfully
  7. 7. Validate that the /modules/messaging/ endpoint is patched by confirming path traversal is no longer possible
  8. 8. Review Splunk logs for any post-upgrade errors
Caveat Review Splunk release notes for breaking changes between your current version and target version; test upgrade in non-production environment first

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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