# CVE-2022-32156: Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation

> Attackers can intercept CLI traffic via MITM because TLS certificate validation is disabled by default, requiring manual configuration to fix.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-775p-gpqh-xf63

## What is CVE-2022-32156?

CVE-2022-32156 is a high-severity vulnerability in Splunk Splunk, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-32156?

It affects 2 products.


Products: Splunk Splunk, Splunk Universal Forwarder.

## How do I fix CVE-2022-32156?

No fix has been published for CVE-2022-32156 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-32156 being exploited?

There is no known exploitation of CVE-2022-32156 in the wild and no public exploit code.

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32156 and fix it if it is affected.

What it is: CVE-2022-32156 is a high-severity vulnerability in Splunk Splunk, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-32156 in the wild and no public exploit code.

Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-32156/ (Markdown: https://insights.sbomify.com/CVE-2022-32156/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32156
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32156
- OSV: https://osv.dev/vulnerability/CVE-2022-32156

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-32156/
Summaries are generated and may contain mistakes; the official description above is the record.