Service interruption via crafted search macros
Published Nov 4, 2022 · Updated May 1, 2025
Resource exhaustion in Splunk Enterprise before 8.1.12, 8.2.9, and 9.0.2 allows remote authenticated users to interrupt service. The REST API search parser processes specially crafted search macros with ignore_parse_error=t without adequately bounding resource use. Exploitation requires permission to create search macros and schedule search reports, and the documented consequence is service denial without data exposure or modification.
Summary
What happened
Resource exhaustion in Splunk Enterprise before 8.1.12, 8.2.9, and 9.0.2 allows remote authenticated users to interrupt service. The REST API search parser processes specially crafted search macros with ignore_parse_error=t without adequately bounding resource use. Exploitation requires permission to create search macros and schedule search reports, and the documented consequence is service denial without data exposure or modification.
The record
- CVE
- CVE-2022-43564
- Published
- Nov 4, 2022
- Updated
- May 1, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2022CVE publishedPublication date reported by the CVE source.
- May 1, 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