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

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2024
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-36v8-vqh8-c3xx

## 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 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-29945?

It affects 1 product.


Products: 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](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29945 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2024-29945 in the wild and no public exploit code.

Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-29945/ (Markdown: https://insights.sbomify.com/CVE-2024-29945/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29945
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29945
- OSV: https://osv.dev/vulnerability/CVE-2024-29945

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-29945/
Summaries are generated and may contain mistakes; the official description above is the record.