Splunk Enterprise: XML Injection
CVE-2023-46214 is a high-severity XML injection vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 9.0.7, 9.1.2 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 89.2% chance of exploitation within 30 days, which is in the top 0.22% of all scored CVEs.
Exploitation in the next 30 days is more likely than not, according to EPSS.
What to do
- Update Splunk Enterprise to 9.0.7 or 9.1.2, whichever matches your release line, or a later version.
- Update Splunk Cloud to 9.1.2308 or a later version.
- Update Cloud to 9.1.2308 or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 9.0 up to, but not including, 9.0.7; 9.1 up to, but not including, 9.1.2 | 9.0.7, 9.1.2 |
| Splunk | Splunk Cloud | before 9.1.2308 | 9.1.2308 |
| Splunk | Cloud | before 9.1.2308 | 9.1.2308 |
| Splunk | Splunk | 9.0.0 up to, but not including, 9.0.7; 9.1.0 up to, but not including, 9.1.2 | 9.0.7, 9.1.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.0 | High | CNA (splunk.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply. This means that an attacker can upload malicious XSLT which can result in remote code execution on the Splunk Enterprise instance.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: XML Injection
The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Recent XML Injection vulnerabilities
- 9.8 Critical severity
- 8.0 High severity
- 8.2 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.