Content injection via unsanitized relative URI path
Published May 6, 2022 · Updated Aug 3, 2024
Path traversal in Splunk Web in Splunk Enterprise before 8.1.2 allows remote attackers to inject content through a crafted relative URI. The search parameter handler fails to sanitize the URI path used to load a relative resource, enabling HTML or script injection and bypasses of risky-command safeguards. Exploitation requires Splunk Web to be enabled and a victim to initiate the crafted request in a browser, such as by following a phishing link.
Summary
What happened
Path traversal in Splunk Web in Splunk Enterprise before 8.1.2 allows remote attackers to inject content through a crafted relative URI. The search parameter handler fails to sanitize the URI path used to load a relative resource, enabling HTML or script injection and bypasses of risky-command safeguards. Exploitation requires Splunk Web to be enabled and a victim to initiate the crafted request in a browser, such as by following a phishing link.
The record
- CVE
- CVE-2022-26889
- Published
- May 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-22, CWE-20, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=Version(s) before 8.1.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