CVE-2023-22934 json
SPL Command Safeguards Bypass via the ‘pivot’ SPL Command in Splunk Enterprise
published 2023-02-14 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-27036
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
In Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4, the ‘pivot’ search processing language (SPL) command lets a search bypass SPL safeguards for risky commands using a saved search job. The vulnerability requires an authenticated user to craft the saved job and a higher privileged user to initiate a request within their browser.
Patch / fix
- Splunk Splunk Enterprise 8.1.13, 8.2.10, 9.0.4
- Splunk Splunk Cloud Platform 9.0.2209.3
- splunk splunk 8.1.13, 8.2.10, 9.0.4
- splunk splunk_cloud_platform 9.0.2209.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- research.splunk.com https://research.splunk.com/application/ee69374a-d27e-4136-adac-956a96ff60fd referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Cloud Platform
- splunk splunk
- splunk splunk_cloud_platform
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
research.splunk.com
/application/ee69374a-d27e-4136-adac-956a96ff60fd
exploit, vendor-advisory
-
advisory.splunk.com
/advisories/SVD-2023-0204
vendor-advisory
Sources
- CVE List CVE-2023-22934
- NVD CVE-2023-22934
Fencer Vulns 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.