dbcve.org
SplunkApplication

CVE-2024-45736

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-14
Fix available
A fix is available. Upgrade to 9.1.6 / 9.1.2312.111 or later.
See remediation →
71/100
Remediation priority · Elevated
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 versions below 9.3.1, 9.2.3, and 9.1.6 and Splunk Cloud Platform versions below 9.2.2403.107, 9.1.2312.204, and 9.1.2312.111, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a search query with an improperly formatted "INGEST_EVAL" parameter as part of a [Field Transformation](https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Managefieldtransforms) which could crash the Splunk daemon (splunkd).

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 denial of service vulnerability in Splunk Enterprise and Cloud Platform allows authenticated low-privilege users to crash the splunkd daemon by submitting search queries with improperly formatted INGEST_EVAL parameters within Field Transformations. The vulnerability does not require admin or power roles, only valid authentication.

MitigationUpgrade Splunk Enterprise to versions 9.3.1, 9.2.3, 9.1.6 or later, or upgrade Splunk Cloud Platform to versions 9.2.2403.107, 9.1.2312.204, 9.1.2312.111 or later to patch this vulnerability.

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
Splunk Cloud PlatformApplication
Affected:>= 9.1.2312, < 9.1.2312.111>= 9.1.2312.200, < 9.1.2312.204>= 9.2.2403.100, < 9.2.2403.107

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check Splunk Enterprise version
    Run: splunk version or inspect $SPLUNK_HOME/etc/splunk.version
    Affected if The installed version is 9.1.0 through 9.1.5.x, 9.2.0 through 9.2.2.x, or exactly 9.3.0 (for Splunk Enterprise)
  2. Check Splunk Cloud Platform version
    View the version in Splunk Cloud Portal or run: | rest /services/server/info | fields version
    Affected if The installed version is 9.1.2312.0 through 9.1.2312.110, 9.1.2312.200 through 9.1.2312.203, or 9.2.2403.100 through 9.2.2403.106 (for Splunk Cloud Platform)
  3. Identify Field Transformations using INGEST_EVAL
    Search for INGEST_EVAL in transforms.conf: grep -r "INGEST_EVAL" $SPLUNK_HOME/etc/system/default/transforms.conf $SPLUNK_HOME/etc/system/local/transforms.conf $SPLUNK_HOME/etc/apps/*/transforms.conf 2>/dev/null
    Affected if Any Field Transformation with INGEST_EVAL fields is configured in the environment
  4. Check for recent splunkd crashes
    Review splunkd crash logs: ls -la $SPLUNK_HOME/var/log/splunk/splunkd.log* | head -20; grep -i "crash\|fatal\|abort" $SPLUNK_HOME/var/log/splunk/splunkd.log 2>/dev/null | tail -50
    Affected if splunkd has recently crashed with no other clear cause, especially after search queries

You are affected if your Splunk version falls within the affected ranges AND Field Transformations with INGEST_EVAL are configured in your environment, allowing any authenticated user to trigger the denial of service.

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.111 / 9.1.2312.204 or later
Fixed in 9.1.69.1.2312.1119.1.2312.204
Interim mitigation

Upgrade Splunk Enterprise to versions 9.3.1, 9.2.3, 9.1.6 or later, or upgrade Splunk Cloud Platform to versions 9.2.2403.107, 9.1.2312.204, 9.1.2312.111 or later to patch this vulnerability.

Recommended fix High confidence

Splunk Enterprise: 9.1.6+, 9.2.3+, 9.3.1+ | Splunk Cloud Platform: 9.1.2312.111+, 9.1.2312.204+, 9.2.2403.107+

  1. 1. Review current Splunk deployment and identify the exact version running (Splunk Enterprise or Splunk Cloud Platform)
  2. 2. For Splunk Enterprise: If running 9.1.x, upgrade to 9.1.6 or later; if running 9.2.x, upgrade to 9.2.3 or later; if running 9.3.0, upgrade to 9.3.1 or later
  3. 3. For Splunk Cloud Platform: Contact Splunk Support to request the upgrade to the fixed version (9.1.2312.111, 9.1.2312.204, or 9.2.2403.107 or later)
  4. 4. After upgrade, verify splunkd service is running and stable
  5. 5. Test that Field Transformations with INGEST_EVAL work correctly in the upgraded version
Caveat Standard Splunk upgrade considerations apply - review Splunk documentation for migration notes between major versions, particularly for custom field transformations and search head cluster 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
  • 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-45736 — 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-45736 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