CVE-2022-43570 XML External Entity Injection through a custom View in Splunk Enterprise
An authenticated user can exploit an XML External Entity injection in Splunk Enterprise to embed incorrect documents into errors, potentially leading to data exposure.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-43570?
CVE-2022-43570 is a high-severity vulnerability in Splunk Splunk, published on 4 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-611
Which versions are affected by CVE-2022-43570?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2022-43570?
No fix has been published for CVE-2022-43570 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-43570 being exploited?
There is no known exploitation of CVE-2022-43570 in the wild and no public exploit code.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-wcm6-qr3c-r573.