SPL Injection through the Mission Control REST API in Splunk Enterprise Security
概要
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_view_im_data capability could cause the Mission Control incident mapping Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| SplunkSplunk Enterprise Security |
8.7.0 未満→ 8.7.0 |
8.7.0 |
原文の説明 取得元が公開している説明をそのまま載せています (多くは英語)。
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_view_im_data capability could cause the Mission Control incident mapping Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could expose all data in Splunk indexes and all stored credentials and modify protected indexes and lookup data.
The vulnerability is possible because the Mission Control incident mapping REST API does not validate incident identifiers before including them in SPL searches.
For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.
出典: CVE.org (CVE Program・cvelistV5) NVD
参照URL
- web psirt@cisco.com