| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In Splunk SOAR versions below 8.8.0, an authenticated Splunk SOAR user with permission to edit and run playbooks could read action status and callback state from a playbook run outside the authorized container-label or tenant scope for that user.
The vulnerability is possible because the playbook API uses mutable runtime context to identify a playbook run instead of preserving the server-provided context. |
| In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission for the container label on a pending approval could read an external-prompt capability through an Approval details Representational State Transfer (REST) API response and use it to view the prompt content, change the pending approval decision, and modify its action parameters.
The vulnerability is possible because an Approval details response exposes the external-prompt capability without checking approval ownership.
For more information see REST External Prompt (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.5.0/external-prompt-endpoints/rest-external-prompt) and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation. |
| In Splunk SOAR versions below 8.8.0, a user with edit permission for the container label of a pending external prompt could obtain the external prompt link through the Representational State Transfer (REST) API and use the link to view and resolve the associated approval.
The vulnerability is possible because the approval detail REST API includes the external prompt link in responses outside the assigned approval scope.
For more information see REST Approval (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.3.1/approval-endpoints/rest-approval), REST External Prompt (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/7.1.0/external-prompt-endpoints/rest-external-prompt), and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation. |
| In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could modify a child playbook callback handle associated with another playbook run, which could alter the callback behavior of that run.
The vulnerability exists because the Playbook API does not verify that callback-handle updates belong to the related parent and child playbook runs. |
| In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view an affected container could query the Representational State Transfer (REST) API for approvals to retrieve a live external prompt link belonging to another user. Using this link, the user could read the approval prompt without authentication and submit a response, potentially disrupting or altering the automated workflow governed by that approval.
The vulnerability is possible because the REST API for approvals exposes the live external prompt link without verifying that the requester owns the approval. |
| In Splunk SOAR versions below 8.8.0, a user that holds a role with the containers:view permission could access automation history for containers outside the label or tenant scope assigned to the user. This could expose action parameters, connector result summaries, and other investigation and response activity.
The vulnerability is possible because the Splunk SOAR Representational State Transfer (REST) API checks the permission to view containers but does not restrict automation history to containers within the label or tenant scope assigned to the user.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) and Configure multiple tenants on your Splunk SOAR (On-premises) instance (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/configure-product-settings-for-your-splunk-soar-on-premises-instance/configure-multiple-tenants-on-your-splunk-soar-on-premises-instance) in the Splunk documentation. |
| In Splunk SOAR versions below 8.8.0, a user with edit permission for containers on only a subset of container labels could modify container pins outside the container labels that the role permits.
The vulnerability is possible because the Container Pin Representational State Transfer (REST) API does not enforce the container label authorization boundary when handling requests.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation. |
| In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the Ingestion Status history through the Representational State Transfer (REST) API. When another user with permission to view system settings retrieves the Ingestion Status history, Splunk SOAR could use additional resources and return a larger response, which could degrade the availability of administrative monitoring.
The vulnerability is possible because Splunk SOAR does not limit the amount of request data that it records for failed container creation before it stores the data in the Ingestion Status history.
For more information see REST Containers (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.4.0/container-endpoints/rest-containers), REST Roles and Permissions (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.4.0/role-management-endpoints/rest-roles-and-permissions), and View ingested container statistics using Ingestion Status (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/manage-your-splunk-soar-on-premises-system-health-and-performance/view-ingested-container-statistics-using-ingestion-status) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row.
The vulnerability is possible because the System Update Status report does not validate destination, signature, and vendor-product values before inserting them into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and System Update Status (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/system-update-status) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled certificate values. If another user who can access the Secure Sockets Layer Search dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row.
The vulnerability is possible because the Secure Sockets Layer Search dashboard encodes certificate values for the drilldown link but does not escape the values as SPL search literals before inserting the values into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Protocol intelligence dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/protocol-intelligence-dashboards) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. The user who stores the values could then access sensitive data and modify some data available to the user who selects the drilldown.
The vulnerability is possible because the Weak Encrypted Communication report does not validate source, destination, and Secure Sockets Layer version values before inserting them into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Weak Encrypted Communication (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/weak-encrypted-communication) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user who can influence indexed event data could store attacker-controlled values in event fields. If another authenticated user who reviews the event selects the View Adaptive Response Invocations or View Adaptive Response Results workflow action from Event Actions, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the action. The unauthenticated user could then access or modify sensitive data and disrupt services available to the user who selects the action.
The vulnerability is possible because the affected Common Information Model workflow actions insert the orig_sid and orig_rid event-field values directly into searches without safely validating or quoting the values.
For more information see About workflow actions in Splunk Web (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.2/workflow-actions/about-workflow-actions-in-splunk-web) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in data used by the Credit Card Data Found dashboard. If another user who can access the dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data available to the user who selects the row.
The vulnerability is possible because the Credit Card Data Found dashboard does not validate source and destination values before inserting them into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Credit Card Data Found (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/credit-card-data-found) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could create and deliver an Entity Analysis dashboard link to a Splunk Enterprise Security user. If the Splunk Enterprise Security user opens the link, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the Splunk Enterprise Security user. The commands could expose or modify some data available to the Splunk Enterprise Security user.
The vulnerability is possible because the Entity Analysis dashboard inserts entity values from a link that an unauthenticated user creates into SPL searches without safely escaping the values.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will.
For more information see Entity analysis dashboard (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/exposure-analytics-and-ueba/entity-analysis-dashboard) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in endpoint summary data. If another user who can access the Time Center dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify some data available to the user who selects the row.
The vulnerability is possible because the Time Center dashboard does not safely escape endpoint summary values before inserting them into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Endpoint dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/endpoint-dashboards) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in vulnerability scan data. If another user who can access the Vulnerability Scan Details dashboard selects an affected value, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the value. The user who stores the values could then access sensitive data and modify data available to the user who selects the affected value.
The vulnerability is possible because the Vulnerability Scan Details dashboard does not validate destination values before inserting them into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Vulnerability Scan Details (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/vulnerability-scan-details) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in managed-lookup audit data. If another user who can access the Managed Lookups Audit dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify some data available to the user who selects the row.
The vulnerability is possible because the Managed Lookups Audit dashboard does not safely escape audit data before inserting it into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick a user that holds a role with the ueba_can_view_ui capability into opening a link that the unauthenticated user creates for the User and Entity Behavior Analytics (UEBA) Overview dashboard. When the user opens the link, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opens the link. The commands could expose or modify some data available to the user who opens the link and partially disrupt search processing.
The vulnerability is possible because the User and Entity Behavior Analytics Overview dashboard does not escape dashboard filter values from the link before substituting the values into SPL searches.
The vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will.
For more information see UEBA dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.8/analytics/ueba-dashboards) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in vulnerability data. If another user who can access the Vulnerability Search dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify some data available to the user who selects the row.
The vulnerability is possible because the Vulnerability Search dashboard encodes data-model field values for the drilldown link but does not escape the values as SPL search literals before inserting the values into drilldown searches.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Network dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/network-dashboards) in the Splunk documentation. |
| In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashboard. If another user who can access the dashboard selects the affected search, Splunk Enterprise Security could run attacker-controlled SPL commands using the permissions of the user who selects the search. The user who runs the first search could then access sensitive data and modify some data available to the user who selects the affected search.
The vulnerability is possible because the Search Audit dashboard does not safely escape logged search text before inserting it into drilldown searches.
For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation. |