Splunk Enterprise: Improper Neutralization of Special Elements used in a Command
CVE-2022-32154 is a high-severity improper neutralization of special elements used in a command vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 8.1 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 version 9.0 as the first without the flaw, so updating Splunk Enterprise to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.45% chance of exploitation within 30 days, higher than 74% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 9.0 or a later version.
- Update Splunk Cloud Platform to 8.2.2106 or a later version.
- Update Splunk to 9.0 or a later version.
- Read the advisory on docs.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 | 9.0 |
| Splunk | Splunk Cloud Platform | 8.2 up to, but not including, 8.2.2106 | 8.2.2106 |
| Splunk | Splunk | before 9.0 | 9.0 |
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
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.8 | Medium | CNA (splunk.com) |
| CVSS 3.1 | 8.1 | High | NVD |
| CVSS 2.0 | 4.0 | Medium | NVD |
Official description
Dashboards in Splunk Enterprise versions before 9.0 might let an attacker inject risky search commands into a form token when the token is used in a query in a cross-origin request. The result bypasses SPL safeguards for risky commands. See New capabilities can limit access to some custom and potentially risky commands (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_limit_access_to_some_custom_and_potentially_risky_commands) for more information. Note that the attack is browser-based and an attacker cannot exploit it at will.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/SPLsafeguards#New_capabilities_can_limit_access_to_some_c…Mitigation
- docs.splunk.com/Documentation/Splunk/9.0.0/Security/UpdatesRelease Notes
- research.splunk.com/application/splunk_command_and_scripting_interpreter_delete_usage/Mitigation
- research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_commands/Mitigation
- research.splunk.com/application/splunk_command_and_scripting_interpreter_risky_spl_mltk/Mitigation
- splunk.com/en_us/product-security/announcements/svd-2022-0604.html
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 Neutralization of Special Elements used in a Command vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.