Authorization Bypass in the REST API in Splunk SOAR
Summary
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 AP...
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| SplunkSplunk SOAR |
< 8.8.0→ 8.8.0 |
8.8.0 |
Original description The description as published by the source.
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.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web psirt@cisco.com