CVE-2022-43563: Risky command safeguards bypass via rex search command field names in Splunk Enterprise
First published: Fri Nov 04 2022(Updated: )
In Splunk Enterprise versions below 8.2.9 and 8.1.12, the way that the rex search command handles field names lets an attacker bypass SPL safeguards for risky commands https://docs.splunk.com/Documentation/SplunkCloud/latest/Security/SPLsafeguards . 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.
Credit: prodsec@splunk.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Splunk Splunk | >=8.1.0<8.1.12 | |
| Splunk Splunk | >=8.2.0<8.2.9 | |
| Splunk Splunk Cloud Platform | <9.0.2203 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the vulnerability ID of this vulnerability?
The vulnerability ID is CVE-2022-43563.
What is the severity of CVE-2022-43563?
The severity of CVE-2022-43563 is high.
Which versions of Splunk Enterprise are affected by CVE-2022-43563?
Splunk Enterprise versions below 8.2.9 and 8.1.12 are affected by CVE-2022-43563.
What is the impact of CVE-2022-43563?
CVE-2022-43563 allows an attacker to bypass SPL safeguards for risky commands in Splunk Enterprise.
How can I fix CVE-2022-43563?
To fix CVE-2022-43563, upgrade to Splunk Enterprise version 8.2.9 or 8.1.12.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/severity
- agent/tags
- agent/references
- agent/first-publish-date
- agent/title
- agent/description
- agent/event
- vendor/splunk
- canonical/splunk splunk
- version/splunk splunk/8.1.0
- version/splunk splunk/8.2.0
- canonical/splunk splunk cloud platform