CVE-2023-32710
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 · uneditedIn Splunk Enterprise versions below 9.0.5, 8.2.11, and 8.1.14, and in Splunk Cloud Platform versions below 9.0.2303.100, a low-privileged user can perform an unauthorized transfer of data from a search using the ‘copyresults’ command if they know the search ID (SID) of a search job that has recently run.
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 confidenceA low-privileged Splunk user can execute the 'copyresults' command to transfer data from any search job if they know that search's SID (Search ID), bypassing proper authorization controls. This allows unauthorized data exfiltration from searches run by other users.
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>= 8.1.0, < 8.1.14>= 8.2.0, < 8.2.11>= 9.0.0, < 9.0.5< 9.0.2303.100CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionRun 'splunk version' or check $SPLUNK_HOME/etc/splunk.version fileAffected if Version is 8.1.0-8.1.13, 8.2.0-8.2.10, or 9.0.0-9.0.4 (or Splunk Cloud Platform is below 9.0.2303.100)
-
Verify copyresults command permissionsNavigate to Settings > Roles in Splunk Web and inspect each role's Capabilities list for 'search' capability, or check authorization.conf for copyresults command restrictionsAffected if Low-privileged roles (such as 'user' or 'power') have access to the copyresults command without proper SID ownership checks
-
Review audit logs for copyresults usageSearch the _internal index: index=_internal sourcetype=splunkd component=Executables search="copyresults" OR search="copyresults" | table _time user search_idAffected if There are entries showing users executing copyresults on search jobs they did not create (search_id owned by different users)
-
Check for unauthorized search job accessSearch audit logs for search_id values where the 'user' field differs from the 'creator' field: index=_internal sourcetype=scheduler | stats by search_id user creatorAffected if Low-privileged users are accessing search jobs created by other users through copyresults
The environment is affected if running a vulnerable Splunk version AND low-privileged users can access the copyresults command to exfiltrate data from searches they did not create.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.1.148.2.119.0.5
Upgrade Splunk Enterprise to version 9.0.5, 8.2.11, or 8.1.14 (or Splunk Cloud Platform to 9.0.2303.100) to patch the authorization bypass in the copyresults command.
Splunk Enterprise: 8.1.14, 8.2.11, or 9.0.5+ | Splunk Cloud Platform: 9.0.2303.100+
- Upgrade Splunk Enterprise to version 8.1.14 or higher if running 8.1.x
- Upgrade Splunk Enterprise to version 8.2.11 or higher if running 8.2.x
- Upgrade Splunk Enterprise to version 9.0.5 or higher if running 9.0.x
- For Splunk Cloud Platform customers, upgrade to version 9.0.2303.100 or higher (managed by Splunk)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,528.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32710 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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