In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_timeline capability could store attacker-controlled Search Processing Language (SPL) in a legacy investigation timeline entry. Another user that holds a role with the manage_all_investigations capability could later open the investigation and select Run Search from the timeline. Splunk Enterprise Security could then run the SPL stored by the first user using the permissions of the user who selected Run Search. The SPL stored by the first user could access data or perform actions available to the user who selected Run Search.
The vulnerability is possible because Splunk Enterprise Security does not treat stored investigation search content as a literal search before building the Search page link.
For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.3/installation/capability-reference-for-splunk-enterprise-security) and Add details to an investigation in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-7/user-guide/7.3/investigations/add-details-to-an-investigation-in-splunk-enterprise-security) in the Splunk documentation.
Bu kayıt NIST NVD kaynağından aktarılmıştır. Etkilenen sürümler, güncel değerlendirme ve üretici referansları için kaynak kaydı inceleyin.

