SPL Injection through the rename Command in Splunk Enterprise
概要
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using the permissions of the user who opens the dashboard. With t...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| SplunkSplunk Enterprise |
10.4 以上 10.4.5 未満→ 10.4.5 10.2 以上 10.2.9 未満→ 10.2.9 10.0 以上 10.0.12 未満→ 10.0.12 9.4 以上 9.4.17 未満→ 9.4.17 |
10.4.5 10.2.9 10.0.12 9.4.17 |
原文の説明 取得元が公開している説明をそのまま載せています (多くは英語)。
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using the permissions of the user who opens the dashboard. With this access, the user who created the dashboard could expose stored credentials and write data to an index.
The vulnerability is possible because Splunk Enterprise does not correctly escape field names in searches that use the rename command.
For more information see rename (https://help.splunk.com/en/splunk-enterprise/spl-search-reference/10.4/search-commands/rename) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.
出典: CVE.org (CVE Program・cvelistV5) NVD
参照URL
- web psirt@cisco.com