Vulnerabilities · 2022 · Splunk
CVE-2022-32156
Splunk vulnerability
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.
Affected products
Splunk, Universal Forwarder. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Splunk runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Config · Mitigation
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates · Vendor Advisory
- www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html · Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-32156
- cve.org/CVERecord?id=CVE-2022-32156
More vulnerabilities in Splunk products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.