CVE-2023-32712

Unauthenticated Log Injection in Splunk Enterprise

LOW
3.1
CVSS Score
Published: June 1, 2023 at 04:34 PM UTC
Updated: June 17, 2026 at 05:59 AM UTC
2 products affected across 1 vendorSplunkUniversal Forwarder

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.1
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

8.1.0 ≤ v < 8.1.148.2 ≤ v < 8.2.11.28.2.0 ≤ v < 8.2.119.0 ≤ v < 9.0.5.19.0.0 ≤ v < 9.0.59.1 ≤ v < 9.1.0.28.29.09.1
Affected range stops below 8.1.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.11.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.0.5.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.1.0.2, so it looks safe — our inference, not a vendor statement
8.2 ≤ v < 8.2.129.0 ≤ v < 9.0.69.1 ≤ v < 9.1.18.29.09.1
Affected range stops below 8.2.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.0.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.1.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-117CWE-116

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card