Restricted-content access via REST response splitting
Published Jun 1, 2023 · Updated Feb 28, 2025
HTTP response splitting in Splunk Web allows remote authenticated users to access restricted REST content through the rest SPL command. The published CWE mapping establishes that Splunk Web fails to neutralize CR and LF characters before including data in outgoing HTTP headers. A low-privileged account is required in Splunk Enterprise 8.1.0 through 8.1.13, 8.2.0 through 8.2.10, and 9.0.0 through 9.0.4, or Splunk Cloud Platform before 9.0.2303.100; successful exploitation reaches arbitrary REST endpoints.
Summary
What happened
HTTP response splitting in Splunk Web allows remote authenticated users to access restricted REST content through the rest SPL command. The published CWE mapping establishes that Splunk Web fails to neutralize CR and LF characters before including data in outgoing HTTP headers. A low-privileged account is required in Splunk Enterprise 8.1.0 through 8.1.13, 8.2.0 through 8.2.10, and 9.0.0 through 9.0.4, or Splunk Cloud Platform before 9.0.2303.100; successful exploitation reaches arbitrary REST endpoints.
The record
- CVE
- CVE-2023-32708
- Published
- Jun 1, 2023
- Updated
- Feb 28, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-436, CWE-113
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Feb 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.1 <8.1.14
- Affected versionversion=8.2 <8.2.11
- Affected versionversion=9.0 <9.0.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo