Cyber Resilience

CVE-2023-32708

Splunk 8.1.0 – 8.1.14

Published
01 June 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0075 52th percentile
Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2023-32708 is a high-severity HTTP Request/Response Splitting (CWE-113) vulnerability in Splunk Splunk. Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 InjectionA06:2025 Insecure Design

EU & UK References

Vulnerability Data

In Splunk Enterprise versions below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform versions below 9.0.2303.100, a low-privileged user can trigger an HTTP response splitting vulnerability with the ‘rest’ SPL command that lets them potentially access other REST endpoints in…

more

the system arbitrarily.

CWE(s)
CWE-113CWE-436

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 →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-20388Same product: Splunk Splunk
CVE-2025-20322Same product: Splunk Splunk
CVE-2024-45737Same product: Splunk Splunk
CVE-2024-36994Same product: Splunk Splunk
CVE-2025-20297Same product: Splunk Splunk
CVE-2026-20258Same product: Splunk Splunk
CVE-2025-20321Same product: Splunk Splunk
CVE-2026-20252Same product: Splunk Splunk
CVE-2023-22932Same product: Splunk Splunk
CVE-2024-45741Same product: Splunk Splunk

Affected Assets

splunk
splunk
8.1.0 — 8.1.14 · 8.2.0 — 8.2.11 · 9.0.0 — 9.0.5
splunk
splunk cloud platform
≤ 9.0.2303.100

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)
  • V3.4.2
  • V4.1.3
  • V1.3.6
  • V4.2.3

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 directly require input sanitization and header handling that prevent CRLF injection.

DE.AE-03 partial match
prevents

Correlating logs from multiple products can surface discrepancies caused by interpretation conflicts.

DE.CM-09 partial match
prevents

Runtime monitoring of software behavior can detect adverse outcomes stemming from differing interpretations.

GV.SC-07 partial match
prevents

Supplier risk assessments can identify products whose differing interpretations create systemic exposure.

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.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect CRLF injection flaws before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection into HTTP headers.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including HTTP header manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of header-splitting vulnerabilities through proper component isolation.

A.8.28 Secure coding partial match
prevents

Secure coding standards require neutralization of CRLF sequences before inclusion in HTTP headers.

A.8.15 Logging none match
none

Logging of HTTP traffic can record header-splitting attempts, aiding detection and forensics.

References