# CVE-2022-32151: Splunk Enterprise disabled TLS validation using the CA certificate stores in Python 3 libraries by default

> Splunk Enterprise failed to validate TLS certificates by default, allowing potential man-in-the-middle attacks against internal communications.

- **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:** 15 Jun 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4mv8-3862-hghv

## What is CVE-2022-32151?

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

### 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.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 2 products.


Products: Splunk Splunk, Splunk Splunk Cloud Platform.

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

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

## Is CVE-2022-32151 being exploited?

There is no known exploitation of CVE-2022-32151 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-32151 and fix it if it is affected.

What it is: CVE-2022-32151 is a high-severity vulnerability in Splunk Splunk, published on 15 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-32151 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-32151/ (Markdown: https://insights.sbomify.com/CVE-2022-32151/index.md)
```

## Sources

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

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