How severe is CVE-2024-29945?

CVE-2024-29945 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-29945 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (57th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-29945?

CVE-2024-29945 affects Splunk. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-29945?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-29945 have an EU (EUVD) identifier?

Yes. CVE-2024-29945 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-26919.

When was CVE-2024-29945 published?

CVE-2024-29945 was published on 2024-03-27 and last updated on 2026-06-17.

CVE-2024-29945

CVE-2024-29945 is a high-severity vulnerability in Splunk with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 1% (57th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-26919
Weakness: CWE-532
Affected product: Splunk
Published: 2024-03-27
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2024-29945?: 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.
How severe is CVE-2024-29945?: CVE-2024-29945 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-29945 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (57th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-29945?: CVE-2024-29945 affects Splunk. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-29945?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-29945 have an EU (EUVD) identifier?: Yes. CVE-2024-29945 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-26919.
When was CVE-2024-29945 published?: CVE-2024-29945 was published on 2024-03-27 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*

More vulnerabilities in Splunk

CVE-2026-20253 — Critical (CVSS 9.8): In Splunk Enterprise 10.2 versions below 10.2.4 and 10 versions below 10.0.7, an unauthenticated user could create or…
CVE-2017-17067 — Critical (CVSS 9.8): Splunk Web in Splunk Enterprise 7.0.x before 7.0.0.1, 6.6.x before 6.6.3.2, 6.5.x before 6.5.6, 6.4.x before 6.4.9, and…
CVE-2016-10126 — Critical (CVSS 9.8): Splunk Web in Splunk Enterprise 5.0.x before 5.0.17, 6.0.x before 6.0.13, 6.1.x before 6.1.12, 6.2.x before 6.2.12,…
CVE-2013-6771 — Critical (CVSS 9.3): Directory traversal vulnerability in the collect script in Splunk before 5.0.5 allows remote attackers to execute…
CVE-2011-4644 — Critical (CVSS 9.3): Splunk 4.2.5 and earlier, when a Free license is selected, enables potentially undesirable functionality within an…
CVE-2022-32158 — Critical (CVSS 9.0): Splunk Enterprise deployment servers in versions before 8.1.10.1, 8.2.6.1, and 9.0 let clients deploy forwarder bundles…

All CVEs affecting Splunk →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →