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.

Published: 2022-11-04 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-43570 is rated Moderate Risk (51.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.66%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-43570

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.26% 0.66% +0.39%
2 2025-11-08 0.17% 0.26% +0.09%
3 2025-03-30 — 0.17% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-43570

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2022-43570

Affected software / configurations for CVE-2022-43570

Vendor Product Version Raw CPE
splunk splunk >= 8.1.0, < 8.1.12 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 8.2.0, < 8.2.9 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 9.0.0, < 9.0.2 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk_cloud_platform < 9.0.2209 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*

References for CVE-2022-43570

cvelogic Threat Intelligence