CVE-2022-32153
published 2022-06-15CVE-2022-32153: Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates…
PriorityP346high8.1CVSS 3.1
AVNACHPRNUINSUCHIHAH
EPSS
0.83%
53.0th percentile
Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. For Splunk Enterprise, update to Splunk Enterprise version 9.0 and Configure TLS host name validation for Splunk-to-Splunk communications (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation) to enable the remediation.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| splunk | splunk | < 9.0 | 9.0 |
| splunk | splunk_cloud_platform | < 8.2.2203 | 8.2.2203 |
| splunk_inc | splunk_cloud_platform | >= 8.2 < 8.2.2203 | 8.2.2203 |
| splunk_inc | splunk_enterprise | >= 9.0 < 9.0 | 9.0 |
CVSS provenance
nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationhttps://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updateshttps://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.htmlhttps://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationhttps://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updateshttps://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.html
2022-06-15
Published