Splunk SOAR playbook run state disclosure in playbook API
Splunk SOAR
Splunk SOAR
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk SOAR |
| No fix yet |
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.
From the CVE record · cisco
In Splunk SOAR versions below 8.8.0, the playbook API uses mutable runtime context rather than preserving server-provided context to identify a playbook run. An authenticated user who can edit and run playbooks could read action status and callback state from a run outside their authorized container-label or tenant scope.
Teams running Splunk SOAR versions below 8.8.0 should check their deployments.