{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-3997 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3997 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3997 is a high-severity code injection vulnerability in Splunk SOAR (Cloud), published on 31 Jul 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-3997 and fix it if it is affected.\n\nWhat it is: CVE-2023-3997 is a high-severity code injection vulnerability in Splunk SOAR (Cloud), published on 31 Jul 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-3997 in the wild and no public exploit code.\n\nAffected product: Splunk SOAR (Cloud). 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-3997/ (Markdown: https://insights.sbomify.com/CVE-2023-3997/index.md)","id":"CVE-2023-3997","markdown":"https://insights.sbomify.com/CVE-2023-3997/index.md","name":"CVE-2023-3997","record":{"aliases":["GHSA-48g5-4ph9-jjmf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Splunk SOAR","requires_auth":"none","summary":"Attackers can inject ANSI characters into logs, leading to code execution when users view the poisoned logs in a terminal.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"soar","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":"Splunk SOAR versions lower than 6.1.0 are indirectly affected by a potential vulnerability accessed through the user’s terminal. A third party can send Splunk SOAR a maliciously crafted web request containing special ANSI characters to cause log file poisoning. When a terminal user attempts to view the poisoned logs, this can tamper with the terminal and cause possible malicious code execution from the terminal user’s action.","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 SOAR","id":"CVE-2023-3997","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":"wpDiscuz \u003c= 7.6.3 - Insecure Direct Object Reference to Post Rating Increase/Decrease","id":"CVE-2023-3998"},"packages":[],"prev":{"headline":"ARMember Lite - Membership Plugin \u003c= 4.0.16 - Authenticated (Administrator+) Stored Cross-Site Scripting","id":"CVE-2023-3996"},"products":["Splunk SOAR (Cloud)","Splunk SOAR (On-premises)"],"published":"2023-07-31","related":[{"cvss_score":8.1,"headline":"Authentication Bypass through IP Address Spoofing in the Automation Broker in Splunk SOAR","id":"CVE-2026-76356","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":7.6,"headline":"Remote Code Execution (RCE) through Path Traversal in the REST API in Splunk SOAR","id":"CVE-2026-76357","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":7.4,"headline":"Improper Certificate Validation through CyberArk Vault Privileged Access Manager in Splunk SOAR","id":"CVE-2026-76362","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Path Traversal through App Installation Tar Extraction in Splunk SOAR","id":"CVE-2026-76358","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Path Traversal through Universal Forwarder Installer Archive Extraction in Splunk SOAR","id":"CVE-2026-76359","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Structured Query Language Injection through the REST API in Splunk SOAR","id":"CVE-2026-76363","kev_date_added":null,"published":"2026-08-19"}],"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 characters into logs, leading to code execution when users view the poisoned logs in a terminal.","url":"https://insights.sbomify.com/CVE-2023-3997/"}