CVE-2024-29945 json
Splunk Authentication Token Exposure in Debug Log in Splunk Enterprise
published 2y ago modified 4mo ago also EUVD-2024-26919
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk Splunk Enterprise 9.0.9, 9.1.4, 9.2.1
- splunk splunk 9.0.9, 9.1.4, 9.2.1
Is CVE-2024-29945 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Splunk Splunk Enterprise
- splunk splunk
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
advisory.splunk.com
/advisories/SVD-2024-0301
mitigation, vendor-advisory
-
research.splunk.com
/application/9a67e749-d291-40dd-8376-d422e7ecf8b5
technical-description, vendor-advisory
Sources
- CVE List CVE-2024-29945
- NVD CVE-2024-29945
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.