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

Published Jun 1, 2023
·
Updated

In Splunk Enterprise versions below 9.0.5, 8.2.11, and 8.1.14, an attacker can use a specially crafted web URL in their browser to cause log file poisoning. The attack requires the attacker to have secure shell (SSH) access to the instance and use a terminal program that supports a certain feature set to execute the attack successfully.

Other sources

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 Software

3 affected components
Splunk splunk>=8.1.0<8.1.14
Splunk splunk>=8.2.0<8.2.11
Splunk splunk>=9.0.0<9.0.5

Event History

Jun 1, 2023
CVE Published
via MITRE·04:34 PM
Data Sourced
via MITRE·04:34 PM
DescriptionSeverityWeakness
Data Sourced
05:15 PM
Description
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the vulnerability ID of this Splunk vulnerability?

The vulnerability ID is CVE-2023-32712.

2

What is the severity of CVE-2023-32712?

The severity of CVE-2023-32712 is high with a CVSS score of 3.1.

3

Which versions of Splunk Enterprise are affected by CVE-2023-32712?

Splunk Enterprise versions below 9.1.0.2, 9.0.5.1, and 8.2.11.2 are affected by CVE-2023-32712.

4

What is the impact of CVE-2023-32712?

An attacker can inject ANSI escape codes into Splunk log files that can potentially result in code execution in vulnerable terminal applications.

5

Where can I find more information about CVE-2023-32712?

You can find more information about CVE-2023-32712 at the following references: [Splunk Advisory](https://advisory.splunk.com/advisories/SVD-2023-0606) and [Splunk Research](https://research.splunk.com/application/de3908dc-1298-446d-84b9-fa81d37e959b).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203