Skip to content
Fencer Intel
high 8.1

CVE-2024-29946 json

Risky command safeguards bypass in Dashboard Examples Hub

published 2y ago modified 4mo ago also EUVD-2024-26920

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

In Splunk Enterprise versions below 9.2.1, 9.1.4, and 9.0.9, the Dashboard Examples Hub lacks protections for risky SPL commands. This could let attackers bypass SPL safeguards for risky commands in the Hub. The vulnerability would require the attacker to phish the victim by tricking them into initiating a request within their browser.

Patch / fix

  • Splunk Splunk Enterprise 9.0.9, 9.1.4, 9.2.1
  • Splunk Splunk Cloud Platform 9.1.2308.205, 9.1.2312.104
  • splunk splunk 9.0.9, 9.1.4, 9.2.1
  • splunk cloud 9.1.2308.205, 9.1.2312.104

Is CVE-2024-29946 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected products

  • Splunk Splunk Enterprise
  • Splunk Splunk Cloud Platform
  • splunk splunk
  • splunk cloud

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

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.