In Splunk SOAR versions below 8.8.0, a user with a role limited to the apps:edit permission can exploit a vulnerability to install a connector app that writes attacker-controlled files outside the intended app directory. This allows modification of files used by Splunk SOAR and execution of arbitrary code with the privileges of the Splunk SOAR user account. The issue arises because the dependency installation command is constructed from app metadata without proper validation, enabling argument manipulation.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with System Settings view and edit permissions can cause the platform to send a stored directory service account bind password to an attacker-controlled host during an LDAP authentication test. This occurs because the system reuses stored credentials when testing authentication against different directory service destinations.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with System Settings edit permission can execute arbitrary code on the host. This occurs because the REST API accepts package references from untrusted sources and passes them to the dependency installer without sufficient validation.
In Splunk SOAR versions below 8.8.0, a user with permissions to create and view containers for a specific label can exploit the REST API to create a container referencing a workbook phase in a case they are not authorized to view. This leads to disclosure of the phase name and inconsistent phase associations due to insufficient authorization checks in the Container REST API during container creation.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with edit permissions on container or workbook tasks can inject attacker-controlled HTML into notes. When viewed by users with view permissions, this can lead to execution of unauthorized JavaScript in their browsers, potentially exposing data and allowing actions via the authenticated session. This occurs because active content is not properly neutralized before rendering in Mission Control.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with roles permitting asset editing or deletion and access to one or more tenants can modify or delete assets assigned to other tenants via the REST API. This occurs because the system verifies permissions but does not confirm tenant access for the target asset. Exploitation could lead to redirection of connector traffic, exposure of credentials and operational data, and disruption of integrations and data ingestion for other tenants.
Splunk SOAR versions below 8.8.0 contain a critical vulnerability where an authenticated user with specific edit and execute permissions can exploit the App Wizard to run arbitrary code as the Splunk SOAR service user. This flaw arises from improper validation of user-supplied identifiers in the App Wizard, risking full compromise of the system's confidentiality, integrity, and availability.
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permissions to view and edit containers and at least one container label can set misleading user and app provenance on containers they create. This occurs because the REST API accepts client-supplied values for server-managed container fields, allowing the user to also infer the existence of user IDs and installed app identifiers.
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with containers:edit permission can import a container with a malicious HTML note. When another user views this note, unauthorized JavaScript may execute in their browser, potentially exposing data and allowing actions with that user's privileges. This occurs because HTML note content is not sanitized during import before rendering in Mission Control.
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to create containers on one label can create a container referencing a parent container they cannot access. This allows alteration of incident lineage across authorization boundaries and identification of restricted containers. The issue arises because the REST API accepts a user-supplied parent container without verifying access permissions to that container.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an unauthenticated user can gain administrator privileges by exploiting a flaw in the user-management REST API. The issue arises because the API incorrectly interprets numeric role names as role identifiers, allowing privilege escalation through role assignment.
In Splunk SOAR versions below 8.8.0, a user with permission to view and modify containers labeled as allowed can add artifacts to containers they are not authorized to view or modify. This occurs due to improper enforcement of authorization boundaries in the REST API artifact-creation workflow.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with System Settings edit permission and restricted tenant access can modify settings of tenants outside their scope via the REST API. This flaw arises because the Tenant REST API verifies the edit permission but fails to enforce tenant restrictions, allowing unauthorized access to tenant configurations. Exploitation could lead to exposure of confidential tenant data, unauthorized changes to tenant settings and automation, or disruption of tenant operations.
In Splunk SOAR versions below 8.8.0, a user with edit permission on the container label of a pending external prompt can access the external prompt link via the REST API. This link allows the user to view and resolve the associated approval, bypassing intended approval scope restrictions. The vulnerability arises because the approval detail REST API exposes the external prompt link in responses beyond the assigned approval scope.
In Splunk SOAR versions below 8.8.0, an authenticated user with permissions to edit and run playbooks could access action status and callback state information from playbook runs outside their authorized container-label or tenant scope. This occurs due to the playbook API using mutable runtime context rather than preserving server-provided context to identify playbook runs.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permission to edit and run playbooks can modify a child playbook callback handle associated with another playbook run. This occurs because the Playbook API does not verify that callback-handle updates belong to the related parent and child playbook runs, potentially altering the callback behavior of that run.
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to edit containers for an allowed label can forge the author attribution of container pins and access user details beyond their authorization. This occurs because the Container Pin REST API does not properly restrict caller-provided author fields, allowing reassignment of pin authors and unauthorized querying of user-related data.
In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission on the container label of a pending approval can exploit a vulnerability in the Approval details REST API. This flaw allows the user to read an external-prompt capability without verifying approval ownership, enabling them to view prompt content, alter the pending approval decision, and modify action parameters.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permissions to view, edit, and run playbooks and access at least one container label can retrieve a callback handle from a playbook run outside their container-label scope. This occurs because the system does not verify that the callback handle belongs to the parent playbook run that launched the child playbook. The vulnerability has a CVSS score of 4.3, indicating medium severity.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permission to view a container can access the REST API to retrieve a live external prompt link for approvals belonging to other users. This link allows reading and responding to approval prompts without further authentication, potentially disrupting automated workflows.