dbcve.org
SplunkApplication

CVE-2022-37437

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
When using Ingest Actions to configure a destination that resides on Amazon Simple Storage Service (S3) in Splunk Web, TLS certificate validation is not correctly performed and tested for the destination. The vulnerability only affects connections between Splunk Enterprise and an Ingest Actions Destination through Splunk Web and only applies to environments that have configured TLS certificate validation. It does not apply to Destinations configured directly in the outputs.conf configuration file. The vulnerability affects Splunk Enterprise version 9.0.0 and does not affect versions below 9.0.0, including the 8.1.x and 8.2.x versions.

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

In Splunk Enterprise 9.0.0, TLS certificate validation is incorrectly bypassed when configuring S3 destinations through Ingest Actions in Splunk Web, allowing potential man-in-the-middle attacks. This only affects connections through Splunk Web in environments with TLS certificate validation enabled, not destinations configured in outputs.conf.

MitigationUpgrade Splunk Enterprise 9.0.0 to a patched version, or configure S3 destinations directly in outputs.conf instead of through Splunk Web.

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

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
High

CVSS:3.1/AV:N/AC:L/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. Verify Splunk Enterprise version
    Check the installed Splunk Enterprise version. In Splunk Web, go to Settings > About > Version information, or run 'splunk --version' from the command line.
    Affected if The installed version is exactly 9.0.0
  2. Identify S3 destination configuration method
    Review how S3 destinations for Ingest Actions are configured. Check if they were created through Splunk Web via Settings > Ingest Actions, or if they are defined in outputs.conf on the forwarder or indexer.
    Affected if S3 destinations are configured through Splunk Web Ingest Actions rather than directly in outputs.conf
  3. Confirm TLS certificate validation status
    Check whether TLS certificate validation is enabled in the Splunk environment. This is typically configured in the server.conf or in the SSL settings within Splunk Web for HTTPS connections.
    Affected if TLS certificate validation is enabled in the Splunk environment
  4. Check for active S3 ingest actions
    Review Ingest Actions configurations in Splunk Web at Settings > Ingest Actions to identify any active S3-based destinations.
    Affected if There are active S3 destinations configured through Splunk Web Ingest Actions with TLS validation enabled

A user is affected if they run Splunk Enterprise 9.0.0 with S3 destinations configured through Splunk Web Ingest Actions while TLS certificate validation is enabled in their environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Splunk Enterprise 9.0.0 to a patched version, or configure S3 destinations directly in outputs.conf instead of through Splunk Web.

Recommended fix High confidence

Splunk Enterprise 9.0.1 or later (latest 9.0.x release)

  1. 1. Download the latest Splunk Enterprise 9.0.x maintenance release (e.g., 9.0.1 or later) from the official Splunk website
  2. 2. Review Splunk upgrade documentation for pre-upgrade checklist items
  3. 3. Create a full backup of your Splunk environment including configuration files and the underlying data
  4. 4. Stop the Splunk Enterprise instance
  5. 5. Install the new version (upgrade) following Splunk's standard upgrade procedure
  6. 6. Start the Splunk Enterprise instance after installation completes
  7. 7. Verify that the Ingest Actions destination configuration works correctly in Splunk Web
  8. 8. Confirm TLS certificate validation is now properly enforced for S3 destinations configured through Ingest Actions
Caveat Review Splunk 9.0.x release notes for any configuration or feature changes between 9.0.0 and the target version; test in non-production environment first

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 help mitigating

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-37437 — 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-37437 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