Authentication token disclosure via DEBUG validation logging
Published Mar 27, 2024 · Updated Dec 16, 2025
Sensitive data exposure in Splunk Enterprise before 9.0.9, 9.1.4, and 9.2.1 allows attackers to obtain authentication tokens from logs. JsonWebToken validation writes token values into splunkd DEBUG events when global or component-level DEBUG logging is active. Exposure requires enabled token authentication plus local log access or administrative access to internal indexes; these features are disabled or restricted by default.
Summary
What happened
Sensitive data exposure in Splunk Enterprise before 9.0.9, 9.1.4, and 9.2.1 allows attackers to obtain authentication tokens from logs. JsonWebToken validation writes token values into splunkd DEBUG events when global or component-level DEBUG logging is active. Exposure requires enabled token authentication plus local log access or administrative access to internal indexes; these features are disabled or restricted by default.
The record
- CVE
- CVE-2024-29945
- Published
- Mar 27, 2024
- Updated
- Dec 16, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-532, T1552.001, T1654
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.0 <9.0.9
- Affected versionversion=9.1 <9.1.4
- Affected versionversion=9.2 <9.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo