CVE-2024-29945 Splunk Authentication Token Exposure in Debug Log in Splunk Enterprise
Attackers can steal authentication tokens from debug logs in Splunk Enterprise, potentially leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-29945?
CVE-2024-29945 is a high-severity vulnerability in Splunk Splunk, published on 27 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
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.
Weakness: CWE-532
Which versions are affected by CVE-2024-29945?
It affects 1 product.
Products include Splunk Splunk.
How do I fix CVE-2024-29945?
No fix has been published for CVE-2024-29945 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-29945 being exploited?
There is no known exploitation of CVE-2024-29945 in the wild and no public exploit code.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-36v8-vqh8-c3xx.