Skip to content
VulniPulse
Advisory severityHigh8.6Splunk

High [CVE-2023-4571] In Splunk IT Service Intelligence (ITSI) versions below below 4.13.3, 4.15.3, or 4.17.1, a malicious actor

This high-severity Splunk advisory covers CVE-2023-4571; related products: IT Service Intelligence, ITSI.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2023-4571 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
SplunkES / ITSI / SOAR
Open source advisory

Android app · Google Play

Monitor future Splunk CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected versions
  • 4.13.3
  • 4.15.3
  • 4.17.1

Official advisory · high-confidence parse· fetched 3 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 3 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 3 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.