dbcve.org
SplunkApplication

CVE-2023-22939

HIGH · 8.8 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 8.1.13 / 8.2.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 versions below 8.1.13, 8.2.10, and 9.0.4, the ‘map’ search processing language (SPL) command lets a search bypass SPL safeguards for risky commands. The vulnerability requires a higher privileged user to initiate a request within their browser and only affects instances with Splunk Web enabled.

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

The 'map' SPL command in Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4 allows a search to bypass SPL safeguards for risky commands. This SPL injection vulnerability enables a higher-privileged user to execute restricted SPL commands through a crafted browser request, but only affects instances with Splunk Web enabled.

MitigationUpgrade Splunk Enterprise to versions 8.1.13, 8.2.10, 9.0.4 or higher, or disable Splunk Web if it is not required.

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.13>= 8.2.0, < 8.2.10>= 9.0.0, < 9.0.4
Splunk Cloud PlatformApplication
Affected:< 9.0.2209.3

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Web is enabled
    Check the $SPLUNK_HOME/etc/system/default/web.conf file or run: splunk cmd python -c 'import splunk.admin; print(splunk.rest.getServerInfo()["serverinfo"]["web_port"])' to confirm Splunk Web is listening on a port
    Affected if Splunk Web is enabled (required condition - the vulnerability only affects instances with Splunk Web active)
  2. Check installed Splunk Enterprise version
    Run: splunk version or look at $SPLUNK_HOME/splunk-version.txt
    Affected if Version is 8.1.0 to 8.1.12, 8.2.0 to 8.2.9, or 9.0.0 to 9.0.3 (falls within the vulnerable version ranges)
  3. Confirm Splunk Cloud Platform version
    If using Splunk Cloud, check the Cloud version through the Splunk Cloud management console or API endpoint
    Affected if Version is earlier than 9.0.2209.3 (Cloud versions prior to this patch level)
  4. Verify 'map' command availability
    Review saved searches, dashboards, or SPL logs for usage of the map command, which can be used to inject malicious SPL
    Affected if The 'map' command is accessible to users and Splunk Web is enabled on a vulnerable version

An environment is affected if Splunk Web is enabled AND the installed Splunk version falls within the vulnerable ranges (8.1.0-8.1.12, 8.2.0-8.2.9, 9.0.0-9.0.3, or Splunk Cloud below 9.0.2209.3).

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.13 / 8.2.10 / 9.0.4 or later
Fixed in 8.1.138.2.109.0.4
Interim mitigation

Upgrade Splunk Enterprise to versions 8.1.13, 8.2.10, 9.0.4 or higher, or disable Splunk Web if it is not required.

Recommended fix High confidence

8.1.13, 8.2.10, or 9.0.4 (or later for Splunk Enterprise; 9.0.2209.3 or later for Splunk Cloud Platform)

  1. Identify current Splunk version by checking $SPLUNK_HOME/etc/splunk.version or via Splunk Web > About page
  2. If running Splunk Enterprise 8.1.x, upgrade to version 8.1.13 or later
  3. If running Splunk Enterprise 8.2.x, upgrade to version 8.2.10 or later
  4. If running Splunk Enterprise 9.0.x, upgrade to version 9.0.4 or later
  5. If running Splunk Cloud Platform, contact Splunk support to ensure the instance is updated to version 9.0.2209.3 or later
  6. After upgrade, verify the version via Splunk Web or CLI: ./splunk version
  7. Confirm the map command now properly enforces SPL safeguards for risky commands
Caveat Review Splunk upgrade documentation for compatibility notes; test in non-production environment first; custom apps or configs may need adjustment

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

Fix this in Splunk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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