LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43570: XML External Entity Injection through a custom View in Splunk Enterprise

In 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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Splunk Enterprise and lets a logged-in user abuse XML handling in a custom View. The impact is serious because the CVSS rating indicates potential loss of confidentiality, integrity, and availability. It is not listed as known exploited in the provided KEV signal.

Executive priority

Treat this as high priority for Splunk environments because Splunk often holds sensitive operational and security data. Patch affected instances promptly, especially where many users can access Splunk Web.

Technical view

CVE-2022-43570 is a CWE-611 XXE issue in Splunk Enterprise before 8.1.12, 8.2.9, and 9.0.2. An authenticated user can trigger XXE through a custom View, causing Splunk Web to embed incorrect documents into an error. CVSS v3.1 is 8.8.

Likely exposure

Organizations running Splunk Enterprise 8.1, 8.2, or 9.0 below the fixed versions are potentially exposed. Exposure depends on authenticated user access to Splunk Web and use or management of custom Views.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The attack requires authentication, but the CVSS vector shows low complexity, network reachability, no user interaction, and high impact across confidentiality, integrity, and availability.

Researcher notes

Evidence is limited to the CVE record and Splunk advisory metadata in the bundle. The issue is authenticated XXE through custom Views; do not assume unauthenticated exploitation, public exploit availability, or broader Splunk product impact from these sources.

Mitigation direction

  • Upgrade Splunk Enterprise to 8.1.12, 8.2.9, 9.0.2, or later.
  • Review Splunk advisory SVD-2022-1110 for deployment-specific guidance.
  • Restrict Splunk Web access to trusted users and networks while patching.
  • Review who can create or modify custom Views.
  • Monitor Splunk Web errors for suspicious XML or custom View activity.

Validation and detection

  • Inventory Splunk Enterprise versions across all search heads and Splunk Web nodes.
  • Flag versions below 8.1.12, 8.2.9, or 9.0.2.
  • Confirm patched nodes report the expected fixed or later version.
  • Review custom Views for unexpected or untrusted changes.
  • Check Splunk Web logs for unusual errors involving custom Views.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-43570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-43570Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SplunkSplunk Enterprise8.1, 8.2, 9.0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.