CVE-2022-32156
Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation
In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties. The issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Splunk Enterprise Splunk |
≥ 0; < 9.0.0 (affected, custom)
Other versions: unaffected |
CNA: Splunk |
| Universal Forwarder Splunk |
≥ 0; < 9.0.0 (affected, custom)
Other versions: unaffected |
CNA: Splunk |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
NVD applicability configurations (1)
These expressions retain AND/OR operators, negation, and required environmental products. A listed product is not sufficient to establish exposure when additional conditions apply.
[
{
"negate": false,
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
"versionEndExcluding": "9.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:splunk:universal_forwarder:*:*:*:*:*:*:*:*",
"versionEndExcluding": "9.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
]CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.4 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA: Splunk |
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA: Splunk |
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | NVD: [email protected] |
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | NVD: [email protected] |
| 2.0 / 6.8 medium |
AV:N/AC:M/Au:N/C:P/I:P/A:P | NVD: [email protected] |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.htmlCNA: Splunk
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesCNA: Splunk
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLICNA: Splunk
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.htmlADP: CVE · x_transferred
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesADP: CVE · x_transferred
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLIADP: CVE · x_transferred
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI[email protected] · Mitigation, Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates[email protected] · Release Notes, Vendor Advisory
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html[email protected] · Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLIaf854a3a-2127-422b-91ae-364da2661108 · Mitigation, Vendor Advisory
- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updatesaf854a3a-2127-422b-91ae-364da2661108 · Release Notes, Vendor Advisory
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.htmlaf854a3a-2127-422b-91ae-364da2661108 · Vendor Advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.