Splunk Enterprise lacked TLS host name certificate validation
Advisory ID: SVD-2022-0603 Published: 2022-06-14 CVSSv3.1 Score: 8.1, High CWE: CWE-297 CSAF: 2022-06-14-svd-2022-0603 |
CVE ID: CVE-2022-32153 Last Update: 2022-06-14 CVSSv3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Bug ID: SPL-202894 Security Content: |
Description
Communications between Splunk nodes and trusted hosts lacked TLS certificate host name validation in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. The vulnerability requires compromising a valid certificate within the Splunk certificate authority (CA) chain for the specific customer environment or a trusted machine’s chain prior to performing a machine-in-the-middle attack.
For Splunk Enterprise, update to Splunk Enterprise version 9.0 or higher and Configure TLS host name validation to enable the remediation.
At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties.
Solution
For Splunk Enterprise, upgrade to version 9.0 or higher and Configure TLS host name validation.
For Splunk Cloud Platform customers, Splunk is actively patching and monitoring Splunk Cloud instances.
Product Status
Product | Affected Versions |
---|---|
Splunk Enterprise | Versions before 9.0 |
Splunk Cloud Platform | Versions before 8.2.2203 |
Acknowledgments
Chris Green at Splunk