dbcve.org
SplunkApplication

CVE-2022-37439

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-16
Fix available
A fix is available. Upgrade to 8.1.11 / 8.2.7.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
In Splunk Enterprise and Universal Forwarder versions in the following table, indexing a specially crafted ZIP file using the file monitoring input can result in a crash of the application. Attempts to restart the application would result in a crash and would require manually removing the malformed file.

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 · moderate confidence

A denial of service vulnerability exists in Splunk Enterprise and Universal Forwarder where indexing a specially crafted ZIP file through the file monitoring input causes the application to crash. The crash persists across restart attempts, requiring manual removal of the malformed file to recover.

MitigationRestrict or disable file monitoring inputs for untrusted directories, validate ZIP files before indexing, and apply vendor patches when available.

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:>= 8.1.0, < 8.1.11>= 8.2.0, < 8.2.7.1
Universal ForwarderApplication
Affected:>= 8.1.0, < 8.1.11>= 8.2.0, < 8.2.7.1

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify Splunk product and version
    Run 'splunk version' from the Splunk bin directory or check $SPLUNK_HOME/etc/splunk.version
    Affected if The installed version falls within >= 8.1.0, < 8.1.11 or >= 8.2.0, < 8.2.7.1 for either Splunk Enterprise or Universal Forwarder
  2. Confirm file monitoring inputs are configured
    Check inputs.conf for [monitor://] stanzas in $SPLUNK_HOME/etc/system/local/ or $SPLUNK_HOME/etc/apps/*/local/
    Affected if File monitoring inputs (monitor://) are enabled and pointing to directories containing ZIP files
  3. Locate monitored directories containing ZIP files
    Review the paths specified in [monitor://] stanzas and check for .zip files in those directories using 'find <path> -name "*.zip"'
    Affected if ZIP files exist in directories monitored by Splunk inputs
  4. Check Splunk service status
    Run 'splunk status' or check if the splunkd process is running; examine splunkd.log for crashes related to ZIP file processing
    Affected if Splunk service is not running or has crashed, especially after processing a ZIP file
  5. Identify recently added or modified ZIP files in monitored paths
    Use 'ls -lat' on directories from monitor:// stanzas to list recently modified ZIP files, or check splunkd.log for entries referencing the ZIP file that triggered the crash
    Affected if A recently created or modified ZIP file exists in a monitored directory and the application has crashed or cannot start

You are affected if you run Splunk Enterprise or Universal Forwarder within the vulnerable version ranges AND have file monitoring inputs configured for directories containing ZIP files that could contain the specially crafted content.

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.1.11 / 8.2.7.1 or later
Fixed in 8.1.118.2.7.1
Interim mitigation

Restrict or disable file monitoring inputs for untrusted directories, validate ZIP files before indexing, and apply vendor patches when available.

Recommended fix High confidence

8.1.11 (or later 8.1.x) / 8.2.7.1 (or later 8.2.x)

  1. 1. Identify all affected Splunk Enterprise and Universal Forwarder installations in your environment
  2. 2. Plan an upgrade during a scheduled maintenance window to minimize service disruption
  3. 3. Back up your Splunk configuration and data before proceeding with the upgrade
  4. 4. For Splunk Enterprise versions 8.1.0-8.1.10, upgrade to version 8.1.11 or later
  5. 5. For Splunk Enterprise versions 8.2.0-8.2.7, upgrade to version 8.2.7.1 or later
  6. 6. Apply the same version upgrades to Universal Forwarder installations
  7. 7. After upgrading, verify the Splunk services start successfully
  8. 8. Test that file monitoring inputs handle ZIP files correctly
Caveat Standard Splunk upgrade considerations apply - review Splunk upgrade documentation for your specific version jump for any configuration or compatibility notes

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

Fix this in Splunk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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