Splunk Enterprise: Improper Control of Generation of Code
CVE-2022-43571 is a high-severity improper control of generation of code 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 attacker with a low-privileged account, without any action from a user. The record lists versions 8.1.12, 8.2.9, 9.0.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 18.6% chance of exploitation within 30 days, which is in the top 2.69% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Splunk Enterprise to 8.1.12 or 8.2.9 or 9.0.2, whichever matches your release line, or a later version.
- Update Splunk to 8.1.12 or 8.2.9 or 9.0.2, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to 9.0.2209 or a later version.
- Read the advisory on research.splunk.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 8.1 up to, but not including, 8.1.12; 8.2 up to, but not including, 8.2.9; 9.0 up to, but not including, 9.0.2 | 8.1.12, 8.2.9, 9.0.2 |
| Splunk | Splunk | 8.1.0 up to, but not including, 8.1.12; 8.2.0 up to, but not including, 8.2.9; 9.0.0 up to, but not including, 9.0.2 | 8.1.12, 8.2.9, 9.0.2 |
| Splunk | Splunk Cloud Platform | before 9.0.2209 | 9.0.2209 |
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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- 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:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA (splunk.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through the dashboard PDF generation component.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, 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 Improper Control of Generation of Code vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.2 High severity
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
Spotted an error? Tell us.