CVE-2022-43566 json
Risky command safeguards bypass via Search ID query in Analytics Workspace in Splunk Enterprise
published 4y ago modified 4mo ago also EUVD-2022-46562
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can run risky commands using a more privileged user’s permissions to bypass SPL safeguards for risky commands https://docs.splunk.com/Documentation/SplunkCloud/latest/Security/SPLsafeguards in the Analytics Workspace. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The attacker cannot exploit the vulnerability at will.
Patch / fix
- Splunk Splunk Enterprise 8.1.12, 8.2.9, 9.0.2
Is CVE-2022-43566 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- research.splunk.com https://research.splunk.com/application/b6d77c6c-f011-4b03-8650-8f10edb7c4a8/ 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
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
research.splunk.com
/application/b6d77c6c-f011-4b03-8650-8f10edb7c4a8/
exploit, vendor-advisory
-
splunk.com
/en_us/product-security/announcements/svd-2022-1106.html
vendor-advisory
Sources
- CVE List CVE-2022-43566
- NVD CVE-2022-43566
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.