CyberRota Analysis
AI-GeneratedIn Splunk SOAR versions prior to 8.6.0, users with the playbooks:view permission can access metadata of playbook repositories they should not be authorized to view due to inadequate permission checks in the Playbook History feature. This could lead to unauthorized exposure of sensitive playbook information. Organizations using affected versions of Splunk SOAR should prioritize updating to mitigate potential information leakage risks.
Original NVD Description
In Splunk SOAR versions below 8.6.0, a user who holds a role that contains the playbooks:view permission could view metadata about a playbook repository that they are not authorized to view. The vulnerability is possible because Playbook History does not check repository permissions before returning playbook revision metadata. For more information see Manage roles and permissions in Splunk SOAR (Cloud) (https://help.splunk.com/en/splunk-soar/soar-cloud/administer-soar-cloud/manage-your-splunk-soar-cloud-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-cloud) and Manage settings for a playbook in Splunk SOAR (Cloud) (https://help.splunk.com/en/splunk-soar/soar-cloud/build-playbooks/manage-playbooks-and-playbook-settings/manage-settings-for-a-playbook-in-splunk-soar-cloud) in the Splunk documentation.
Related CVEs
Other vulnerabilities affecting the same vendor(s)