{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4571 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4571 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4571 is a high-severity code injection vulnerability in Splunk ITSI, published on 30 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-4571 and fix it if it is affected.\n\nWhat it is: CVE-2023-4571 is a high-severity code injection vulnerability in Splunk ITSI, published on 30 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-4571 in the wild and no public exploit code.\n\nAffected product: Splunk ITSI. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-4571/ (Markdown: https://insights.sbomify.com/CVE-2023-4571/index.md)","id":"CVE-2023-4571","markdown":"https://insights.sbomify.com/CVE-2023-4571/index.md","name":"CVE-2023-4571","record":{"aliases":["GHSA-cc2j-mf6c-hch7"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Splunk ITSI","requires_auth":"none","summary":"Attackers can inject ANSI escape codes into logs, leading to code execution when users view logs in vulnerable terminal applications.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"it_service_intelligence","vendor":"splunk"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"},{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"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. \n\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Unauthenticated Log Injection in Splunk IT Service Intelligence (ITSI)","id":"CVE-2023-4571","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Chrome","id":"CVE-2023-4572"},"packages":[],"prev":{"headline":"Improper Restriction in NI MeasurementLink Python Services","id":"CVE-2023-4570"},"products":["Splunk ITSI"],"published":"2023-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-02-28","vendors":["Splunk"]},"summary":"Attackers can inject ANSI escape codes into logs, leading to code execution when users view logs in vulnerable terminal applications.","url":"https://insights.sbomify.com/CVE-2023-4571/"}