CVE-2022-43564
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2, a remote user who can create search macros and schedule search reports can cause a denial of service through the use of specially crafted search macros.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA remote authenticated user with permissions to create search macros and schedule search reports can exploit specially crafted search macros to cause denial of service in Splunk Enterprise versions before 8.1.12, 8.2.9, and 9.0.2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 8.1.0, < 8.1.12>= 8.2.0, < 8.2.9< 9.0.2205CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionNavigate to Settings > System > Server information, or run: splunk versionAffected if Version is 8.1.0-8.1.11, 8.2.0-8.2.8, or any 9.0.x version below 9.0.2205 (for Cloud)
-
Verify user permissions for search macro creationGo to Settings > Users and authentication > Roles, or query the Splunk internal index: | rest /services/authorization/roles | table role, capabilities | search capabilities=*search_macro*Affected if Any role grants the 'run_search_macro' or 'edit_search_macro' capability to non-admin users
-
Identify users with scheduled report permissionsReview roles for 'schedule_search' capability: | rest /services/authorization/roles | table role, capabilities | search capabilities=*schedule*Affected if Non-admin roles have the ability to schedule search reports
-
Review existing search macros for suspicious contentGo to Settings > Advanced search > Search macros, or query: | rest /services/saved/searches | search action.search_type=macro | table title searchAffected if Any search macros contain recursive or nested macro calls that could cause resource exhaustion
-
Check for scheduled searches that reference macrosQuery saved searches: | rest /services/saved/searches | search action.trigger.hook!="" OR cron_schedule!="" | table title cron_schedule searchAffected if Scheduled searches reference custom macros that could be exploited
Your Splunk is affected if it runs a version below 8.1.12/8.2.9/9.0.2205 AND any authenticated user has both macro creation and scheduled report permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.1.128.2.99.0.2205
Upgrade Splunk Enterprise to version 8.1.12, 8.2.9, 9.0.2 or later to remediate this vulnerability.
Splunk Enterprise: 8.1.12, 8.2.9, or 9.0.2 (depending on your current major version); Splunk Cloud Platform: 9.0.2205
- Identify the currently running Splunk Enterprise version using the About page in Splunk Web or by running 'splunk --version' from the CLI
- For Splunk Enterprise 8.1.x deployments: Upgrade to version 8.1.12 or later
- For Splunk Enterprise 8.2.x deployments: Upgrade to version 8.2.9 or later
- For Splunk Enterprise 9.0.x deployments: Upgrade to version 9.0.2 or later
- For Splunk Cloud Platform: Contact Splunk Support to schedule an upgrade to version 9.0.2205 or later
- After upgrading, verify the Splunk services are running correctly
- Test that scheduled searches and search macros function normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data