CVE-2022-32153
Last modified
CVE-2022-32153 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. EPSS estimates a 0.83% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk | < 9.0 |
| Splunk | Splunk Cloud Platform | < 8.2.2203 |
References
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationMitigation, Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes, Vendor Advisory
- https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/Mitigation, Vendor Advisory
- https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/Mitigation, Vendor Advisory
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/Mitigation, Vendor Advisory
- https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/Mitigation, Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidationMitigation, Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes, Vendor Advisory
- https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/Mitigation, Vendor Advisory
- https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/Mitigation, Vendor Advisory
- https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/Mitigation, Vendor Advisory
- https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-32153?
How severe is CVE-2022-32153?
How do I fix CVE-2022-32153?
Are you affected by CVE-2022-32153?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
