dbcve.org
SplunkApplication

CVE-2024-29945

HIGH · 7.2 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 9.0.9 / 9.1.4 or later.
See remediation →
78/100
Remediation priority · High
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.2.1, 9.1.4, and 9.0.9, the software potentially exposes authentication tokens during the token validation process. This exposure happens when either Splunk Enterprise runs in debug mode or the JsonWebToken component has been configured to log its activity at the DEBUG logging level.

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

In Splunk Enterprise versions below 9.2.1, 9.1.4, and 9.0.9, authentication tokens are exposed in logs during the token validation process when either debug mode is enabled or the JsonWebToken component logs at DEBUG level, allowing potential credential theft via log file access.

MitigationUpgrade to Splunk Enterprise 9.2.1, 9.1.4, or 9.0.9, or ensure debug mode is disabled and JsonWebToken logging is set above DEBUG level in production environments.

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.9>= 9.1.0, < 9.1.4>= 9.2.0, < 9.2.1

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Check installed Splunk Enterprise version
    Run 'splunk --version' or access the About page in Splunk Web to view the exact version number
    Affected if The installed version is 9.0.0 to 9.0.8, 9.1.0 to 9.1.3, or 9.2.0
  2. Verify debug mode status
    Access Splunk Web, navigate to Settings > Server settings > Debug mode, or check $SPLUNK_HOME/etc/system/local/server.conf for '[debug]' section with 'enableDebug = true'
    Affected if Debug mode is currently enabled
  3. Check JsonWebToken component log level
    Examine $SPLUNK_HOME/etc/system/local/logging.conf or access Splunk Web Settings > Server settings > Logging level. Look for a line setting the JsonWebToken logger to DEBUG level
    Affected if JsonWebToken logger is set to DEBUG level

You are affected if your Splunk version is within 9.0.0-9.0.8, 9.1.0-9.1.3, or 9.2.0 AND either debug mode is enabled or JsonWebToken logging is set to DEBUG level.

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.9 / 9.1.4 / 9.2.1 or later
Fixed in 9.0.99.1.49.2.1
Interim mitigation

Upgrade to Splunk Enterprise 9.2.1, 9.1.4, or 9.0.9, or ensure debug mode is disabled and JsonWebToken logging is set above DEBUG level in production environments.

Recommended fix High confidence

9.0.9 for 9.0.x branches; 9.1.4 for 9.1.x branches; 9.2.1 for 9.2.x branches

  1. 1. Identify current Splunk Enterprise version by navigating to Settings > About > Version or running: splunk version
  2. 2. Determine the appropriate upgrade path based on current version: if on 9.0.x, upgrade to 9.0.9; if on 9.1.x, upgrade to 9.1.4; if on 9.2.x, upgrade to 9.2.1
  3. 3. Review Splunk upgrade prerequisites: https://docs.splunk.com/Documentation/Splunk/current/Installation/UpgradeSteps
  4. 4. Create a backup of Splunk configuration files and perform a test upgrade in a non-production environment
  5. 5. Download the appropriate Splunk Enterprise fixed version from splunk.com
  6. 6. Execute the upgrade following Splunk's standard upgrade procedure
  7. 7. After upgrade, verify the version is correct: splunk version
  8. 8. As a supplementary mitigation, ensure DEBUG logging for JsonWebToken is not enabled in $SPLUNK_HOME/etc/logging.conf or Web.conf unless absolutely necessary for troubleshooting
Caveat Standard Splunk minor version upgrades typically preserve configuration, but always review release notes for breaking changes before upgrading production instances

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

Fix this in Splunk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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