Cyber Resilience

CVE-2023-3997

Splunk Soar ≤ 6.1.0

Published
31 July 2023
Modified
10 December 2024
Patch / advisory
View advisory
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0029 21th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2023-3997 is a high-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Splunk Soar. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 InjectionA09:2025 Security Logging and Alerting Failures

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-117CWE-116

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-4571Same vendor: Splunk
CVE-2023-32712Same vendor: Splunk
CVE-2025-20384Same vendor: Splunk
CVE-2024-0987Shared CWE-116, CWE-117
CVE-2024-56473Shared CWE-116, CWE-117
CVE-2025-3942Shared CWE-116, CWE-117
CVE-2024-8297Shared CWE-116, CWE-117
CVE-2023-1711Shared CWE-116, CWE-117
CVE-2023-7234Shared CWE-116, CWE-117
CVE-2024-22356Shared CWE-116, CWE-117

Affected Assets

splunk
soar
≤ 6.1.0 · ≤ 6.1.0.131

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.2.1
  • V1.2.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-15 Information Output Filtering
addresses: CWE-116 CWE-117

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

AU-1 Policy and Procedures
addresses: CWE-117

Policy and procedures require sanitization and neutralization when generating audit logs to avoid injection issues.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

A.8.16 Monitoring activities partial match
finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for safe output handling and encoding.

References