Improper Access Control in the REST API in Splunk SOAR
Summary
In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not...
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 permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the expected authorization scope.
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.3.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