CVE-2022-43565
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 8.2.9 and 8.1.12, the way that the ‘tstats command handles Javascript Object Notation (JSON) lets an attacker bypass SPL safeguards for risky commands https://docs.splunk.com/Documentation/SplunkCloud/latest/Security/SPLsafeguards . The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser.
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 confidenceIn Splunk Enterprise versions below 8.2.9 and 8.1.12, the tstats command improperly handles JSON data in a way that bypasses SPL (Search Processing Language) safeguards designed to restrict risky commands. An attacker can exploit this by phishing a victim into initiating a crafted request in their browser, allowing the attacker to potentially execute unsafe SPL commands or access data beyond their authorized permissions.
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.12>= 8.2.0, < 8.2.9< 9.0.2203CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionNavigate to Settings > About or run: splunk --version or check $SPLUNK_HOME/etc/splunk.versionAffected if Version is 8.1.0-8.1.11 or 8.2.0-8.2.8 (for Enterprise)
-
Check Splunk Cloud Platform versionView version information in Splunk Cloud portal under Settings > System > AboutAffected if Version is below 9.0.2203 (for Cloud)
-
Verify tstats command availabilityConfirm tstats is enabled: check $SPLUNK_HOME/etc/default/commands.conf or search for tstats in Settings > CommandsAffected if tstats command is available to users who could be targeted by phishing attempts
-
Review Splunk Web configurationCheck if Splunk Web (splunkd) is exposed externally by reviewing web.conf: $SPLUNK_HOME/etc/system/default/web.confAffected if Splunk Web is accessible from untrusted networks without proper authentication restrictions
You are affected if your Splunk version falls within 8.1.0-8.1.11, 8.2.0-8.2.8 (Enterprise), or below 9.0.2203 (Cloud), and tstats is accessible to users who could be tricked into clicking malicious links.
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.128.2.99.0.2203
Upgrade Splunk Enterprise to version 8.2.9, 8.1.12, or later to patch the vulnerability. Until patched, exercise caution with links and requests originating from untrusted sources, as the exploit requires social engineering to trigger.
Splunk Enterprise: 8.1.12 or 8.2.9; Splunk Cloud Platform: 9.0.2203
- Identify the current Splunk Enterprise or Splunk Cloud Platform version in use
- For Splunk Enterprise 8.1.x: Upgrade to version 8.1.12 or later
- For Splunk Enterprise 8.2.x: Upgrade to version 8.2.9 or later
- For Splunk Cloud Platform: Ensure version is 9.0.2203 or later
- After upgrade, verify the tstats command now properly handles JSON within SPL safeguards
- Review SPL safeguards configuration to ensure protections are active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-43565 — 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-2022-43565 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