Splunk Enterprise・Universal ForwarderのCLIで中間者攻撃を受ける脆弱性
Summary
2022年6月に公表された古い脆弱性です。Splunk Enterpriseと Universal Forwarderの9.0.0より前の版では、CLIがリモートのSplunkへの接続時にTLS証明書を既定では検証せず、中間者攻撃を受けるおそれがあります。修正版は9.0.0で、9.0以降に更新したうえでTLSホスト名検証の設定を有効にしてください。Splunk Cloud Platformには影響しません。
AI summary
Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.
2022年6月に公表された古い脆弱性です。Splunk Enterpriseと Universal Forwarderの9.0.0より前の版では、CLIがリモートのSplunkへの接続時にTLS証明書を既定では検証せず、中間者攻撃を受けるおそれがあります。修正版は9.0.0で、9.0以降に更新したうえでTLSホスト名検証の設定を有効にしてください。Splunk Cloud Platformには影響しません。
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| SplunkSplunk Enterprise |
< 9.0.0→ 9.0.0 |
9.0.0 |
| SplunkUniversal Forwarder |
< 9.0.0→ 9.0.0 |
9.0.0 |
Original description The description as published by the source.
In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties.
The issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- patch splunk.com
- patch docs.splunk.com
- patch docs.splunk.com