同じ製品で同じ時期に公表された 2 件の脆弱性の 1 つです。まとめた解説: Splunk Enterprise更新、認証回避含む脆弱性38件を修正
Authentication Bypass through the RapidDiag REST API in Splunk Enterprise
概要
In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection as an authenticated user. With this access, the user could read or modify data and configuration av...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| SplunkSplunk Enterprise |
10.6 以上 10.6.1 未満→ 10.6.1 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.6.1 10.4.5 10.2.9 10.0.12 9.4.17 |
原文の説明 取得元が公開している説明をそのまま載せています (多くは英語)。
In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could run arbitrary Search Processing Language (SPL) searches through RapidDiag task collection as an authenticated user. With this access, the user could read or modify data and configuration available to that authenticated user.
The vulnerability is possible because Splunk Enterprise accepts an empty shared secret when it authenticates RapidDiag task-collection requests.
For more information see Using RapidDiag (https://help.splunk.com/en/splunk-enterprise/administer/troubleshoot/9.3/contact-splunk-support/using-rapiddiag) in the Splunk documentation.
出典: Cyber Security News NVD