Improper Input Validation through HTTP Event Collector Token Names in Splunk Enterprise
概要
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user holding a role with the edit_token_http capability could create a persistent HTTP Event Collector (HEC) token that cannot be disabled or deleted via the Representational State Transfer (REST) API or Splunk Web. As a resu...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| 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 holding a role with the edit_token_http capability could create a persistent HTTP Event Collector (HEC) token that cannot be disabled or deleted via the Representational State Transfer (REST) API or Splunk Web. As a result, the token remains active and can continue ingesting events even after administrative attempts to revoke it.
The vulnerability is possible because HTTP Event Collector token creation accepts names that later management operations cannot process.
For more information see authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf) and Set up and use HTTP Event Collector in Splunk Web (https://help.splunk.com/en/splunk-enterprise/get-data-in/get-started-with-getting-data-in/10.6/get-data-with-http-event-collector/set-up-and-use-http-event-collector-in-splunk-web) in the Splunk documentation.
出典: CVE.org (CVE Program・cvelistV5) NVD
参照URL
- web psirt@cisco.com