CyberSecBulletin
CVE-2024-29945NVD status: Modified

Splunk Enterprise: Insertion of Sensitive Information into Log File

Published Updated By the CyberSecBulletin desk

CVE-2024-29945 is a high-severity insertion of sensitive information into log file vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 9.2.1, 9.1.4, 9.0.9 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.95% chance of exploitation within 30 days, higher than 62% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Splunk Enterprise to 9.2.1 or 9.1.4 or 9.0.9, whichever matches your release line, or a later version.
  2. Update splunk to 9.0.9 or 9.1.4 or 9.2.1, whichever matches your release line, or a later version.
  3. Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
SplunkSplunk Enterprise9.2 up to, but not including, 9.2.1; 9.1 up to, but not including, 9.1.4; 9.0 up to, but not including, 9.0.99.2.1, 9.1.4, 9.0.9
Splunksplunk9.0 up to, but not including, 9.0.9; 9.1 up to, but not including, 9.1.4; 9.2 up to, but not including, 9.2.19.0.9, 9.1.4, 9.2.1

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.2HighCNA (splunk.com)
CVSS 3.17.2HighNVD

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Splunk Enterprise

All Splunk Enterprise vulnerabilities

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.