CVE-2022-32152
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 1.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.0% in the next 30 days (EPSS).
- Severity: 8.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.0% · EPSS, next 30 days
- Weakness
- CWE-295 · Improper certificate validation
- Record status
- Modified
Affected
- Splunk < 9.0
- Splunk Cloud Platform < 8.2.2203
Attack profile CVSS 3.1 · 8.1
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-32152.md and follow it. Check whether this project is affected by CVE-2022-32152. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://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-0602.html
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/
References
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://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-0602.html
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
- https://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-0602.html