dbcve.org
SplunkApplication

CVE-2023-32708

HIGH · 8.8 CVSS v3.1 Published 2023-06-01
Fix available
A fix is available. Upgrade to 8.1.14 / 8.2.11 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 versions below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform versions below 9.0.2303.100, a low-privileged user can trigger an HTTP response splitting vulnerability with the ‘rest’ SPL command that lets them potentially access other REST endpoints in the system arbitrarily.

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

An HTTP response splitting vulnerability in Splunk Enterprise and Cloud Platform allows low-privileged users to inject malicious content via the 'rest' SPL command, potentially enabling unauthorized access to arbitrary REST endpoints within the system.

MitigationUpgrade Splunk Enterprise to version 9.0.5, 8.2.11, or 8.1.14 (or higher), and Splunk Cloud Platform to 9.0.2303.100 or higher.

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.14>= 8.2.0, < 8.2.11>= 9.0.0, < 9.0.5
Splunk Cloud PlatformApplication
Affected:< 9.0.2303.100

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Splunk Enterprise version
    Run `splunk --version` from the Splunk bin directory, or read the version file at $SPLUNK_HOME/etc/splunk.version
    Affected if the installed version is 8.1.0 through 8.1.13, 8.2.0 through 8.2.10, or 9.0.0 through 9.0.4
  2. Verify Splunk Cloud Platform version
    Check the Splunk Cloud version via the Cloud Portal or by querying the rest endpoint /services/server/info
    Affected if the Cloud Platform version is earlier than 9.0.2303.100
  3. Confirm low-privileged user access to rest command
    Review Splunk roles in etc/system/local/authentication.conf or via the UI at Settings > Access Controls > Roles. Check if users with 'user' or 'power' roles can execute the 'rest' command in SPL
    Affected if low-privileged users (non-admin) have permission to run the 'rest' command in Search

You are affected if your Splunk version falls within the vulnerable ranges AND low-privileged users have access to execute the 'rest' SPL command.

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.14 / 8.2.11 / 9.0.5 or later
Fixed in 8.1.148.2.119.0.5
Interim mitigation

Upgrade Splunk Enterprise to version 9.0.5, 8.2.11, or 8.1.14 (or higher), and Splunk Cloud Platform to 9.0.2303.100 or higher.

Recommended fix High confidence

Splunk Enterprise 9.0.5, 8.2.11, or 8.1.14 (or higher); Splunk Cloud Platform 9.0.2303.100 or higher

  1. 1. Identify the current Splunk Enterprise version by navigating to Settings > About > About Splunk Enterprise, or by running: splunk --version
  2. 2. Determine the appropriate upgrade path based on current version: upgrade to 9.0.5+ if on 9.0.x, upgrade to 8.2.11+ if on 8.2.x, or upgrade to 8.1.14+ if on 8.1.x
  3. 3. For Splunk Cloud Platform customers, verify the current version via the Cloud Portal and confirm the deployment will receive version 9.0.2303.100 or higher
  4. 4. Before upgrading, create a full backup of the Splunk Enterprise configuration: $SPLUNK_HOME/bin/splunk backup <backup_name>
  5. 5. For Splunk Enterprise (not Cloud), download the appropriate installer from https://www.splunk.com/en_us/download.html for the target fixed version
  6. 6. Review Splunk Upgrade Planning documentation at https://docs.splunk.com/Documentation/Splunk/latest/Installation/PlanYourInstallation
  7. 7. Perform the upgrade following Splunk's standard upgrade procedure for the deployment type (standalone, clustered, or distributed)
  8. 8. After upgrade, verify the version matches the target fixed release: splunk --version
Caveat Review Splunk's upgrade compatibility notes - some apps or custom configurations may require updates for major version jumps; 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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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