Splunk Enterprise: Improper Certificate Validation
CVE-2022-32151 is a critical-severity improper certificate validation vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 9.0 as the first without the flaw, so updating Splunk Enterprise to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.81% chance of exploitation within 30 days, higher than 58% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Splunk Enterprise to 9.0 or a later version.
- Update Splunk Cloud Platform to 8.2.2203 or a later version.
- Update Splunk to 9.0 or a later version.
- Read the advisory on docs.splunk.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 9.0 up to, but not including, 9.0 | 9.0 |
| Splunk | Splunk Cloud Platform | 8.2 up to, but not including, 8.2.2203 | 8.2.2203 |
| Splunk | Splunk | before 9.0 | 9.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.4 | High | CNA (splunk.com) |
| CVSS 3.1 | 9.1 | Critical | NVD |
| CVSS 2.0 | 6.4 | Medium | NVD |
Official description
The httplib and urllib Python libraries that Splunk shipped with Splunk Enterprise did not validate certificates using the certificate authority (CA) certificate stores by default in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. Python 3 client libraries now verify server certificates by default and use the appropriate CA certificate stores for each library. Apps and add-ons that include their own HTTP libraries are not affected. 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate.
How developers prevent this class of flaw
- Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
- If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
More Improper Certificate Validation vulnerabilities (CWE-295)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes
- research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_simplerequest/Mitigation
- splunk.com/en_us/product-security/announcements/svd-2022-0601.html
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Recent Improper Certificate Validation vulnerabilities
- 8.1 High severity
- 8.1 High severity
- 7.2 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.