Vulnerabilities · 2022 · Splunk
CVE-2022-32154
Splunk vulnerability
Dashboards in Splunk Enterprise versions before 9.0 might let an attacker inject risky search commands into a form token when the token is used in a query in a cross-origin request. The result bypasses SPL safeguards for risky commands. See New capabilities can limit access to some custom and potentially risky commands (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_limit_access_to_some_custom_and_potentially_risky_commands) for more information. Note that the attack is browser-based and an attacker cannot exploit it at will.
Affected products
Splunk, Splunk Cloud Platform. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Splunk runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_lim · Mitigation
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates · Vendor Advisory
- research.splunk.com/application/splunk_command_and_scripting_interpreter_delete_usage/ · Mitigation
- research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_commands/ · Mitigation
- research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_spl_mltk/ · Mitigation
- www.splunk.com/en_us/product-security/announcements/svd-2022-0604.html · Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-32154
- cve.org/CVERecord?id=CVE-2022-32154
More vulnerabilities in Splunk products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.