In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into managed-lookup audit data. When another user with access to the Managed Lookups Audit dashboard selects an affected row, Splunk may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the dashboard does not properly escape audit data before using it in drilldown searches, potentially allowing unauthorized data access and modification.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the "ess_user" role can run a search that injects attacker-controlled Search Processing Language (SPL) text into the Search Audit dashboard. When another user with access to this dashboard selects the affected search, the attacker-controlled SPL commands execute with the selecting user's permissions. This flaw arises because the Search Audit dashboard does not properly escape logged search text before using it in drilldown searches.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into Network Resolution data. When another user with access to the Domain Name System Search dashboard selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the selecting user's permissions. This occurs because the dashboard encodes data-model field values for drilldown links without properly escaping them as SPL search literals. The vulnerability allows the injecting user to access sensitive data and modify some data accessible to the selecting user.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into vulnerability data. When another user accesses the Vulnerability Search dashboard and selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the dashboard encodes data-model field values for drilldown links but fails to escape them properly as SPL search literals. This flaw could allow unauthorized access to sensitive data and modification of some data accessible to the selecting user.
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated attacker can craft and deliver a malicious Entity Analysis dashboard link to a user. If the user opens the link, attacker-controlled Search Processing Language (SPL) commands may execute with the user's permissions, potentially exposing or modifying data accessible to that user. This vulnerability arises because entity values from the link are inserted into SPL searches without proper escaping. Exploitation requires user interaction via phishing, and the attacker cannot exploit it without tricking a user into opening the link.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into endpoint summary data. When another user accesses the Time Center dashboard and selects an affected row, the system may execute attacker-controlled SPL commands with the permissions of the selecting user. This occurs because the Time Center dashboard does not properly escape endpoint summary values before using them in drilldown searches, potentially allowing unauthorized data access and modification.
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated attacker can craft a malicious link to the User and Entity Behavior Analytics (UEBA) Overview dashboard. If a user with the ueba_can_view_ui capability opens this link, attacker-controlled Search Processing Language (SPL) commands may execute with that user's permissions. This can lead to exposure or modification of data accessible to the user and partial disruption of search processing. Exploitation requires phishing the user to open the malicious link. The vulnerability arises because the dashboard does not properly escape filter values before inserting them into SPL searches.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into the Endpoint Changes report. Another user with the pci_analyst role could trigger the execution of attacker-controlled Search Processing Language (SPL) commands by interacting with the report. This occurs because the report does not properly treat dynamic values as literal search inputs, allowing command injection with the permissions of the clicking user.
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where a user with the run_collect capability can inject attacker-controlled values into Intrusion Detection data. When another user accesses the Intrusion Search dashboard and selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the Intrusion Search dashboard does not properly escape data-model field values before inserting them into drilldown searches, potentially allowing unauthorized data access and modification.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into the Malware data model. Another authenticated user accessing the Malware Search dashboard could trigger execution of attacker-controlled SPL commands with their permissions due to improper quoting of row values in drilldown searches. This could lead to exposure of data accessible to the user and insertion of malicious records into an index.
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where an unauthenticated attacker can craft a malicious link that tricks an authenticated user into executing attacker-controlled Search Processing Language (SPL) commands. This occurs because the Lookup Editor does not properly validate lookup identifiers from URL parameters before including them in searches. Exploitation requires user interaction via phishing, and the attacker cannot exploit the vulnerability without tricking a user. The vulnerability allows access to data and actions permitted to the authenticated user.
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated attacker can craft a malicious Investigation Workbench link that, when opened by an authenticated user, executes arbitrary Search Processing Language (SPL) commands with that user's permissions. This vulnerability arises from improper neutralization of special characters in artifact values. Exploitation requires phishing the user to open the crafted link, as unauthenticated users cannot exploit it directly.
In Splunk Enterprise Security versions below 8.7.0, users with the edit_modinput_identity_manager capability can exploit a vulnerability in Asset and Identity Management to modify protected saved searches and role capabilities, potentially gaining full administrator access. This occurs because the app namespace is not validated before sending REST API requests with system authentication tokens.
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where a user with the run_collect capability can inject attacker-controlled values into the System Misconfigurations report. When another user with access to this report selects a related row, the report may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the report does not properly treat values from the Vulnerabilities data model as literal search values in drilldown searches.
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where users with the mc_investigation_read capability can inject arbitrary Search Processing Language (SPL) into Mission Control dashboard searches. This injection allows Mission Control to execute SPL with elevated permissions, potentially enabling the reading of stored credentials and writing data to indexes and lookups. The issue arises because Mission Control does not validate reserved search filters before incorporating them into dashboard searches.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where users with the ueba_finding_exclusion_edit capability can inject attacker-controlled values into UEBA finding exclusion rules. These values are not properly escaped before being used in generated Search Processing Language (SPL) commands, which are executed with elevated permissions. This allows the user to execute arbitrary SPL commands that can read stored credentials and modify lookups and knowledge objects.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where users with the manage_all_investigations capability can store attacker-controlled script content in legacy investigation workbench panel titles. When another authenticated user opens the affected workbench, the script executes in their browser, potentially exposing data or actions available through Splunk Web. This occurs because legacy panel titles are not properly escaped before rendering.
A vulnerability in Splunk Enterprise Security versions below 8.7.0 allows a user with the "ess_analyst" role to store attacker-controlled data in finding exclusion rule metadata. When another authenticated user opens the Finding Exclusion Rules page, Splunk Enterprise Security may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of that user. This occurs because backslashes in the metadata are not properly escaped before being added to a page search.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into network traffic data. Another user with the pci_user role could then trigger execution of attacker-controlled SPL commands by interacting with the Network Traffic Activity report. This occurs because the report does not properly treat network traffic values as literals when constructing drilldown searches, allowing command execution with the permissions of the clicking user.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into intrusion detection data. A user with the pci_user role can then trigger a report that executes attacker-controlled Search Processing Language (SPL) commands with their permissions. This occurs because the Intrusion Detection and Prevention System Alert Activity report does not properly treat intrusion detection values as literal search inputs when constructing drilldown searches.