Authorization Bypass Through the REST API in Splunk SOAR
Summary
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...
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, 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.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web psirt@cisco.com