ghsa-427f-v2mq-364f
Vulnerability from github
Published
2022-06-16 00:00
Modified
2022-06-25 00:01
Severity ?
Details
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": [], "aliases": [ "CVE-2022-32152" ], "database_specific": { "cwe_ids": [ "CWE-295" ], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2022-06-15T17:15:00Z", "severity": "HIGH" }, "details": "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.", "id": "GHSA-427f-v2mq-364f", "modified": "2022-06-25T00:01:03Z", "published": "2022-06-16T00:00:22Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-32152" }, { "type": "WEB", "url": "https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation" }, { "type": "WEB", "url": "https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates" }, { "type": "WEB", "url": "https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version" }, { "type": "WEB", "url": "https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption" }, { "type": "WEB", "url": "https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned" }, { "type": "WEB", "url": "https://research.splunk.com/network/splunk_identified_ssl_tls_certificates" }, { "type": "WEB", "url": "https://www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ] }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.