Security readout for executives and security teams
Plain-English summary
Splunk SOAR before 6.1.0 can accept crafted web requests that poison logs with terminal control characters. The business risk appears when staff view those logs in a terminal: the terminal display can be tampered with and code execution may result from the user’s action.
Executive priority
Treat this as a high-priority remediation for affected SOAR environments because security operations platforms are sensitive, and terminal-based log review is common during incident response and administration.
Technical view
This is CWE-117 log injection affecting Splunk SOAR On-premises and Cloud versions lower than 6.1.0. The CVSS 3.1 score is 8.6. Attack requires a crafted request and user interaction when logs are viewed in a terminal, with potential high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Splunk SOAR deployments below 6.1.0 where untrusted web requests can reach SOAR and administrators or operators inspect logs through terminal sessions.
Exploitation context
The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The attack is not a simple remote-only path; it depends on poisoned logs being viewed in a terminal by a user.
Researcher notes
The unusual risk chain is unauthenticated log poisoning followed by terminal interpretation during log review. The CVSS vector includes local attack vector and required user interaction, so validation should focus on vulnerable versions and terminal-based log consumption paths.
Mitigation direction
- Upgrade Splunk SOAR versions below 6.1.0 to 6.1.0 or later per Splunk guidance.
- Review Splunk advisory SVD-2023-0702 for current vendor-specific remediation instructions.
- Restrict access to SOAR endpoints to trusted networks where operationally feasible.
- Avoid direct terminal rendering of untrusted SOAR logs until remediation is complete.
- Use log viewers that safely display terminal control characters instead of interpreting them.
Validation and detection
- Inventory Splunk SOAR On-premises and Cloud versions and flag anything below 6.1.0.
- Confirm remediation status against Splunk advisory SVD-2023-0702.
- Identify teams or automation that view SOAR logs in terminal sessions.
- Review relevant logs for unexpected ANSI or terminal control characters using safe viewing tools.
- Verify compensating controls limit untrusted request paths to SOAR where possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-117: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-3997 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H1.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://advisory.splunk.com/advisories/SVD-2023-0702CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Output Neutralization for Logs
Improper Output Neutralization for Logs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.