CVE-2022-43570
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, an authenticated user can perform an extensible markup language (XML) external entity (XXE) injection via a custom View. The XXE injection causes Splunk Web to embed incorrect documents into an error.
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 · high confidenceThis is an XML External Entity (XXE) injection vulnerability in Splunk Enterprise's custom View functionality. An authenticated user can craft malicious XML in a custom view that causes Splunk Web to process external entities and embed incorrect documents into an error response. The vulnerability affects versions below 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.0, < 9.0.2< 9.0.2209CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify installed Splunk Enterprise versionRun the command 'splunk version' from the Splunk installation bin directory, or log into Splunk Web and go to Settings > About > VersionAffected if Version is 8.1.0 through 8.1.11, 8.2.0 through 8.2.8, or 9.0.0 through 9.0.1 (or for Splunk Cloud, version is below 9.0.2209)
-
Confirm Splunk Web interface is enabledCheck that the Splunk Web service is running. This can be verified by attempting to access the Splunk Web URL or by checking the web.conf configuration file in $SPLUNK_HOME/etc/system/default/Affected if Splunk Web is accessible and processing HTTP requests
-
Determine if custom Views are accessible to non-admin usersNavigate to Settings > Visualizations > Custom Views in Splunk Web, or inspect the localapps directory for custom view XML definitions. Review which roles have 'edit_view' or 'write' capabilities for the 'templates' appAffected if Authenticated users with limited privileges can create or modify custom views
The environment is affected if Splunk Enterprise version falls within the vulnerable ranges AND Splunk Web is enabled AND authenticated users have the ability to create or modify custom views.
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.2
Upgrade Splunk Enterprise to version 8.1.12, 8.2.9, 9.0.2 or later. If immediate upgrading is not possible, restrict permissions for creating or modifying custom Views to trusted administrators only.
Splunk Enterprise: upgrade to 8.1.12, 8.2.9, or 9.0.2 | Splunk Cloud Platform: upgrade to 9.0.2209 or later
- Identify your current Splunk Enterprise version using $SPLUNK_HOME/bin/splunk version
- Determine which upgrade path suits your deployment: 8.1.12, 8.2.9, or 9.0.2
- Review Splunk upgrade documentation for your chosen version path
- Plan maintenance window as upgrades require Splunk restart
- Backup your Splunk configuration and deployment state
- For Splunk Cloud customers: Contact Splunk Support to request upgrade to version 9.0.2209 or later
- Execute upgrade following Splunk official upgrade procedures
- Verify the upgrade completed successfully and Splunk services are running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43570 — 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-43570 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