CVE-2023-4571
Assigner: Splunk
Published: 2023-08-30T16:19:39.150Z
State: PUBLISHED
affected: product: Splunk ITSI
vendor: Splunk
versions: version: 4.13
status: affected
versionType: custom
lessThan: 4.13.3
version: 4.15
status: affected
versionType: custom
lessThan: 4.15.3
version: 4.17
status: affected
versionType: custom
lessThan: 4.17.1
descriptions: supportingMedia: base64: no
type: text/html
value: In Splunk IT Service Intelligence (ITSI) versions below below 4.13.3, 4.15.3, or 4.17.1, a malicious actor can inject American National Standards Institute (ANSI) escape codes into Splunk ITSI log files that, when a vulnerable terminal application reads them, can run malicious code in the vulnerable application. This attack requires a user to use a terminal application that translates ANSI escape codes to read the malicious log file locally in the vulnerable terminal. The vulnerability also requires additional user interaction to succeed. 

The vulnerability does not directly affect Splunk ITSI. The indirect impact on Splunk ITSI can vary significantly depending on the permissions in the vulnerable terminal application, as well as where and how the user reads the malicious log file. For example, users can copy the malicious file from Splunk ITSI and read it on their local machine.
value: In Splunk IT Service Intelligence (ITSI) versions below below 4.13.3, 4.15.3, or 4.17.1, a malicious actor can inject American National Standards Institute (ANSI) escape codes into Splunk ITSI log files that, when a vulnerable terminal application reads them, can run malicious code in the vulnerable application. This attack requires a user to use a terminal application that translates ANSI escape codes to read the malicious log file locally in the vulnerable terminal. The vulnerability also requires additional user interaction to succeed. 

The vulnerability does not directly affect Splunk ITSI. The indirect impact on Splunk ITSI can vary significantly depending on the permissions in the vulnerable terminal application, as well as where and how the user reads the malicious log file. For example, users can copy the malicious file from Splunk ITSI and read it on their local machine.
title: Unauthenticated Log Injection in Splunk IT Service Intelligence (ITSI)
datePublic: 2023-08-30T00:00:00.000000
metrics: cvssV3_1: vectorString: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
version: 3.1
baseScore: 8.6
baseSeverity: HIGH
format: CVSS
scenarios: value: GENERAL
problemTypes: descriptions: type: cvw
description: The software does not neutralize or incorrectly neutralizes output that is written to logs.
cweId: CWE-117
source: advisory: SVD-2023-0810
credits: value: STÖK / Fredrik Alexandersson