In Splunk SOAR versions below 8.8.0, users with container edit permissions can supply custom timestamps when creating containers and artifacts via the REST API. This allows manipulation of the timeline displayed to analysts and may cause data retention policies to delete records earlier than intended if such policies are configured.
In Splunk SOAR versions below 8.8.0, users with roles permitting playbook and repository edits can insert modified utility blocks into playbooks. When another user with permission to edit playbook code opens and saves such a playbook, subsequent runs may issue REST API delete requests to unintended resources if the running user has delete permissions. This occurs because Splunk SOAR does not restrict utility blocks from altering REST API request paths.
Splunk SOAR versions below 8.8.0 contain a vulnerability where a local user on the affected host can obtain a live session token or decrypted asset configuration. This occurs when another user initiates an App Editor debug action, which exposes sensitive runtime information to other local users.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with System Settings edit permission can exploit the Automation Dependency Wheel REST API to write arbitrary files outside the intended directory. This improper restriction on uploaded automation dependency wheel filenames can lead to arbitrary code execution.
In Splunk SOAR versions prior to 8.8.0, users with asset edit permissions can modify approval requirements and the effective automation user for an asset without these changes being recorded in field-level audit logs. This lack of audit coverage reduces accountability and weakens investigation capabilities for changes made to security-sensitive asset settings.
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view system settings but without asset access could view asset, app, and container-label metadata in Ingestion filters. This occurs because the system does not enforce asset authorization and tenant restrictions on Ingestion filter metadata. The vulnerability has a medium severity rating with a CVSS score of 4.3.
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit artifacts can cause indicator correlation data to retain stale field associations. This flaw leads to incorrect correlation results and event counts because stale indicator associations are not removed when an artifact changes.
Splunk SOAR versions prior to 8.8.0 have a vulnerability where users with system_settings permission can modify event custom field definitions without these changes being recorded in the audit trail. This lack of auditing reduces forensic visibility and accountability for changes made to custom fields.
In Splunk SOAR versions below 8.8.0, an authenticated user with playbook edit permission can cause later playbook conversions to include incorrect branch conditions. This issue arises because the playbook converter retains branch conditions from previous conversions, potentially preventing downstream blocks from executing in the affected playbooks.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with the 'Observer' role can access password-reset credentials in diagnostic log bundles. This occurs because password-reset email bodies are not redacted before logging, allowing these users to reset passwords for active local accounts.
Splunk SOAR versions below 8.8.0 contain an authorization vulnerability where authenticated users with the System Settings view permission but without the Assets view permission can access asset and tenant metadata via the ingestion history view. This occurs because the ingestion history view does not properly restrict summary results to only those assets and tenants the user is authorized to view.
A vulnerability in Splunk SOAR versions below 8.8.0 allows a user with System Settings edit permission to cause the application to send a stored Elasticsearch password to an attacker-controlled host. This occurs because the application reuses the stored Elasticsearch password when the Search Settings endpoint is changed, without requiring a password replacement.
In Splunk SOAR versions below 8.8.0, a vulnerability exists where a user with the System Settings edit permission can cause the system to send stored root credentials for an external credential store to an attacker-controlled host. This occurs when the user changes the external credential store endpoint without providing replacement credentials, leading to credential exposure. The exposed credentials may include sensitive secrets such as access tokens, application secrets, account passwords, or client certificates.
Splunk SOAR versions below 8.8.0 contain an authorization bypass vulnerability where an authenticated user with permission to view and edit containers for one label can access sensitive product data and credentials outside their authorized scope via a slash command in the REST API. This occurs because the product does not enforce authorization checks on related objects accessed by slash commands from an authorized artifact.
Splunk SOAR versions prior to 8.8.0 contain a vulnerability where an authenticated user with repository edit access can write files outside the configured repository. This occurs because the software does not enforce repository paths to remain within the configured repository boundaries, allowing modification of files accessible by the Splunk SOAR user account.
Splunk SOAR versions below 8.8.0 contain a vulnerability that allows users with the Apps edit permission role to execute arbitrary code as the Splunk SOAR service account by installing a malicious app. This occurs because the platform does not restrict app dependencies to validated binary packages before installation.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with the System Settings edit permission can execute arbitrary code as the Splunk SOAR service account. This occurs due to improper separation between customer automation dependencies and trusted product code.
Splunk SOAR versions prior to 8.8.0 contain a vulnerability where users with the Apps edit permission role can trigger arbitrary code execution on the host by validating an installed app. This occurs because the app validation process does not properly isolate untrusted code from the trusted environment, allowing malicious code execution.
Splunk SOAR versions below 8.8.0 contain an authorization vulnerability where users with the System Settings view permission but without the Assets view permission can access sensitive asset-related information. This includes asset names, identifiers, app names, tenant names, and ingestion schedule settings. The flaw arises because the ingestion schedule view does not properly enforce the Assets view permission before displaying asset-derived data.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permissions to view and edit containers in at least one container label can create artifacts linked to containers and artifacts outside those labels. This flaw allows exposure of fields from restricted artifacts and unauthorized modification of incident lineage due to insufficient verification of access rights to parent containers and artifacts during artifact creation.