{"api_version":"1","generated_at":"2026-07-23T10:53:19+00:00","cve":"CVE-2022-32152","urls":{"html":"https://cve.report/CVE-2022-32152","api":"https://cve.report/api/cve/CVE-2022-32152.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2022-32152","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2022-32152"},"summary":{"title":"CVE-2022-32152","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.","state":"PUBLIC","assigner":"prodsec@splunk.com","published_at":"2022-06-15 17:15:00","updated_at":"2022-06-24 01:23:00"},"problem_types":["CWE-295"],"metrics":[],"references":[{"url":"https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/","name":"https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/","refsource":"CONFIRM","tags":[],"title":"Splunk Digital Certificates Lack of Encryption - Splunk Security Content","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/","name":"https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/","refsource":"CONFIRM","tags":[],"title":"Splunk Digital Certificates Infrastructure Version - Splunk Security Content","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/","name":"https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/","refsource":"CONFIRM","tags":[],"title":"Splunk protocol impersonation weak encryption selfsigned - Splunk Security Content","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation","name":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation","refsource":"CONFIRM","tags":[],"title":"Configure TLS certificate host name validation - Splunk Documentation","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates","name":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates","refsource":"CONFIRM","tags":[],"title":"Security updates - Splunk Documentation","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/","name":"https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/","refsource":"CONFIRM","tags":[],"title":"Splunk Identified SSL TLS Certificates - Splunk Security Content","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html","name":"https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html","refsource":"CONFIRM","tags":[],"title":"SVD-2022-0602 | Splunk","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-32152","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-32152","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"LEGACY","value":"Chris Green at Splunk","lang":""}],"nvd_cpes":[{"cve_year":"2022","cve_id":"32152","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"splunk","cpe5":"splunk","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"enterprise","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2022","cve_id":"32152","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"splunk","cpe5":"splunk_cloud_platform","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"prodsec@splunk.com","DATE_PUBLIC":"2022-06-14T11:55:00.000Z","ID":"CVE-2022-32152","STATE":"PUBLIC","TITLE":"Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"Splunk Enterprise","version":{"version_data":[{"version_affected":"<","version_name":"9.0","version_value":"9.0"}]}},{"product_name":"Splunk Cloud Platform","version":{"version_data":[{"version_affected":"<","version_name":"8.2","version_value":"8.2.2203"}]}}]},"vendor_name":"Splunk"}]}},"credit":[{"lang":"eng","value":"Chris Green at Splunk"}],"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":8.1,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-295 Improper Certificate Validation"}]}]},"references":{"reference_data":[{"name":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation","refsource":"CONFIRM","url":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation"},{"name":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates","refsource":"CONFIRM","url":"https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates"},{"name":"https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html","refsource":"CONFIRM","url":"https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html"},{"name":"https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/","refsource":"CONFIRM","url":"https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version/"},{"name":"https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/","refsource":"CONFIRM","url":"https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/"},{"name":"https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/","refsource":"CONFIRM","url":"https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/"},{"name":"https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/","refsource":"CONFIRM","url":"https://research.splunk.com/network/splunk_identified_ssl_tls_certificates/"}]},"source":{"advisory":"SVD-2022-0602","discovery":"INTERNAL"}},"nvd":{"publishedDate":"2022-06-15 17:15:00","lastModifiedDate":"2022-06-24 01:23:00","problem_types":["CWE-295"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"HIGH","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":7.2,"baseSeverity":"HIGH"},"exploitabilityScore":1.2,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:S/C:P/I:P/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"SINGLE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":6.5},"severity":"MEDIUM","exploitabilityScore":8,"impactScore":6.4,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*","versionEndExcluding":"9.0","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*","versionEndExcluding":"8.2.2203","cpe_name":[]}]}]}},"legacy_mitre":{"record":null,"notes":[]}}}