dbcve.org
SplunkApplication

CVE-2022-32153

HIGH · 8.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 →
90/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
Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. 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 Enterprise peers did not validate TLS certificates during Splunk-to-Splunk communications by default. An attacker with administrator credentials could add a peer without a valid certificate, allowing man-in-the-middle attacks on peer communications. Misconfigured nodes without valid certificates did not fail, enabling interception of encrypted traffic between peers.

MitigationUpdate to Splunk Enterprise 9.0 or Splunk Cloud Platform 8.2.2203 and configure TLS hostname validation for Splunk-to-Splunk communications per Splunk documentation.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed Splunk Enterprise version
    Run: splunk --version or access About > Version in Splunk Web. Compare the version number to 9.0 (e.g., 8.2.x, 8.1.x, 8.0.x).
    Affected if Version is below 9.0 for Splunk Enterprise, or below 8.2.2203 for Splunk Cloud Platform.
  2. Verify if clustering or indexer clustering is enabled
    Check server.conf for [clustering] stanza, or run: splunk show cluster-config. Also check for search head clustering via splunk show shcluster-config.
    Affected if Clustering or any peer replication is enabled, exposing the inter-node communication attack surface.
  3. Check TLS certificate validation setting for server communications
    Inspect server.conf for the sslVerifyServerCert setting in [general] or [sslConfig] sections. Look for: sslVerifyServerCert = false or missing sslVerifyServerCert = true.
    Affected if sslVerifyServerCert is set to false or is absent, meaning certificate validation is disabled.
  4. Check web.conf for SSL settings related to Splunk-to-Splunk communications
    Review $SPLUNK_HOME/etc/system/local/web.conf for [settings] stanza and any httpServerConfig SSL parameters. Check for disabled certificate validation.
    Affected if Web configuration disables certificate verification for peer communications.
  5. Check server.conf for splunktcp SSL configuration
    Look for [splunktcp] stanzas in server.conf and verify sslVerifyServerCert settings. Also check [sslConfig] section for any requireClientCert settings set to false.
    Affected if splunktcp (forwarder-to-indexer communication) has certificate verification disabled.

A system is affected if it runs Splunk Enterprise below 9.0 (or Cloud below 8.2.2203) and has peer clustering/replication enabled with TLS certificate validation disabled or not explicitly configured to true.

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 to Splunk Enterprise 9.0 or Splunk Cloud Platform 8.2.2203 and configure TLS hostname validation for Splunk-to-Splunk communications per Splunk documentation.

Recommended fix High confidence

Splunk Enterprise 9.0 or Splunk Cloud Platform 8.2.2203

  1. Upgrade Splunk Enterprise to version 9.0 or later
  2. Configure TLS hostname validation for Splunk-to-Splunk communications per Splunk documentation (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation)
  3. For Splunk Cloud Platform customers, contact Splunk support to ensure deployment of version 8.2.2203 or later
Caveat Review Splunk 9.0 release notes for any breaking changes before upgrading

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

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32153 — 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-32153 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