Authenticated Blind Server Side Request Forgery via the ‘search_listener’ Search Parameter in Splunk Enterprise

Description

In Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4, the ‘search_listener’ parameter in a search allows for a blind server-side request forgery (SSRF) by an authenticated user. The initiator of the request cannot see the response without the presence of an additional vulnerability within the environment.

Solution

For Splunk Enterprise, upgrade versions to 8.1.13, 8.2.10, 9.0.4, or higher.

For Splunk Cloud Platform, Splunk is actively patching and monitoring the Splunk Cloud instances.

Product Status

Mitigations and Workarounds

This vulnerability requires a user to hold the “search” capability. An administrator can remove this role from user accounts to mitigate the vulnerability. For additional information on Splunk roles, please refer to Define Roles on the Splunk Platform with capabilities.

Detections

• Splunk Risky Command Abuse disclosed February 2023

This hunting search provides information on potential abuse of the ‘search_listener’ search parameter that allows for a blind server-side request forgery by an authenticated user on Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4.

Severity

Splunk rated the vulnerability as Medium, 6.3, with a CVSSv3.1 vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The SSRF requires user access to initiate the search. Further, the initiator of the request cannot see the response without the presence of an additional vulnerability within the environment. As a result, the impact is reduced.

Acknowledgments

Danylo Dmytriiev (DDV_UA)