Skip to main content
VulnerabilityPublished Updated

CVE-2024-29945: Splunk Enterprise · Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.

Affects Splunk EnterpriseSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Splunk Splunk EnterpriseAffected
  • =9.2
  • =9.1
  • =9.0
Fixed in–

AI-suggested

  1. Upgrade Splunk Enterprise to versions 9.2.1, 9.1.4, 9.0.9 or later where this vulnerability is patched.
  2. Immediately audit and disable debug mode in production environments unless strictly necessary for troubleshooting.
  3. Review and adjust logging configurations to ensure the JsonWebToken component is not set to DEBUG logging level in production.
  4. Implement strict access controls and monitoring on log files to prevent unauthorized access, including encryption of logs at rest and in transit.
  5. Conduct regular audits of logging practices and token handling to detect any inadvertent exposure.
  6. Use Splunk’s role-based access controls to limit who can change logging levels or access sensitive logs.
  7. Educate administrators about the risks of verbose logging and enforce policies to restrict debug logging to secure, isolated environments.
  8. Monitor for unusual access patterns to logs and authentication tokens that could indicate exploitation attempts.
  9. Integrate vulnerability management processes to ensure timely application of security patches.

Description

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.

References

Community reviews

Loading reviews…