Script injection and cache poisoning via Host header
Published Nov 4, 2022 · Updated May 5, 2025
Host header injection in Splunk Enterprise Splunk Web allows remote authenticated users to inject scripts through crafted HTTP requests. Splunk Web fails to validate and escape the HTTP Host header before using it in downstream output and server-side behavior. An authenticated, highly privileged account and a crafted request are required; impact is limited to cross-site scripting or cache poisoning, with no direct exploitation technique observed.
Summary
What happened
Host header injection in Splunk Enterprise Splunk Web allows remote authenticated users to inject scripts through crafted HTTP requests. Splunk Web fails to validate and escape the HTTP Host header before using it in downstream output and server-side behavior. An authenticated, highly privileged account and a crafted request are required; impact is limited to cross-site scripting or cache poisoning, with no direct exploitation technique observed.
The record
- CVE
- CVE-2022-43562
- Published
- Nov 4, 2022
- Updated
- May 5, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 4, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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.12
- Affected versionversion=8.2 <8.2.9
- Affected versionversion=9.0 <9.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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