dbcve.org
SplunkApplication

CVE-2022-32151

CRITICAL · 9.1 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 8.2.2203 / 9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Splunk shipped Python httplib and urllib libraries that did not validate SSL/TLS certificates by default, allowing man-in-the-middle attacks on Splunk-to-Splunk communications and outbound HTTP connections. This affects Splunk Enterprise versions before 9.0 and Splunk Cloud Platform before 8.2.2203.

MitigationUpdate Splunk Enterprise to version 9.0 and configure TLS hostname validation per Splunk documentation; Splunk Cloud Platform customers should upgrade to 8.2.2203 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SplunkApplication
Affected:< 9.0
Splunk Cloud PlatformApplication
Affected:< 8.2.2203

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Splunk Enterprise version
    Run the command: splunk version or check $SPLUNK_HOME/etc/system/local/build.yml for the version field
    Affected if The version is below 9.0 (for example, 8.x series)
  2. Check Splunk Cloud Platform version
    In Splunk Cloud, navigate to Settings > Server Settings > Server Information to view the version
    Affected if The version is below 8.2.2203
  3. Identify if Splunk-to-Splunk communications are in use
    Search configuration files (outputs.conf, inputs.conf) for [splunktcp] or [http] stanzas that define inter-Splunk communication
    Affected if Either outputs.conf or inputs.conf contain splunktcp or http event collector endpoints without TLS validation explicitly configured
  4. Check for explicit SSL/TLS certificate validation configuration
    Search for verify_ssl_certs or disable_SSL_certificate_verification settings in $SPLUNK_HOME/etc/system/local/*.conf files, or in any custom app.conf outputs
    Affected if verify_ssl_certs is set to false, disable_SSL_certificate_verification is set to 1, or these settings are absent (relying on default behavior)

You are affected if you run Splunk Enterprise below version 9.0 or Splunk Cloud Platform below 8.2.2203, and your Splunk-to-Splunk or outbound HTTP connections rely on the default Python SSL validation which is disabled by default.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.2.2203 / 9.0 or later
Fixed in 8.2.22039.0
Interim mitigation

Update Splunk Enterprise to version 9.0 and configure TLS hostname validation per Splunk documentation; Splunk Cloud Platform customers should upgrade to 8.2.2203 or later.

Recommended fix High confidence

Splunk Enterprise 9.0 (or Splunk Cloud Platform 8.2.2203)

  1. Upgrade Splunk Enterprise to version 9.0
  2. Configure TLS hostname validation for Splunk-to-Splunk communications by following the documentation at https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
Caveat Ensure all Splunk-to-Splunk communications have valid TLS certificates before enabling hostname validation, or connections may fail

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32151 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data