Security readout for executives and security teams
Plain-English summary
This flaw lets a logged-in Splunk Enterprise user abuse a higher-privileged user’s browser action to run risky SPL commands despite safeguards. It is not an unauthenticated or fully at-will attack, but it can threaten sensitive data and integrity in vulnerable Splunk deployments.
Executive priority
Treat this as a high-priority Splunk maintenance issue where vulnerable versions remain deployed. Business risk is strongest in environments where Splunk contains sensitive operational or security data and many users have interactive access.
Technical view
CVE-2022-43566 affects Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2. In Analytics Workspace, an authenticated attacker can bypass SPL risky-command safeguards by using a Search ID query and a phished victim request, executing with the victim’s higher permissions.
Likely exposure
Exposure is likely limited to Splunk Enterprise 8.1, 8.2, or 9.0 deployments below the fixed versions, especially where Analytics Workspace is available and users have differing privilege levels.
Exploitation context
The source says exploitation requires authentication and user interaction: the attacker must trick a victim into initiating a browser request. The attacker cannot exploit it at will. KEV is false, and the bundle provides no evidence of active exploitation.
Researcher notes
Key constraints matter: PR:L and UI:R, scope unchanged, high confidentiality and integrity impact, no availability impact in CVSS. The bundle identifies CWE-20 but does not provide detailed root-cause mechanics beyond Search ID query handling in Analytics Workspace.
Mitigation direction
- Upgrade affected Splunk Enterprise instances to 8.1.12, 8.2.9, 9.0.2, or later.
- Review Splunk SVD-2022-1106 for vendor-specific guidance and applicability.
- Identify users with access to Analytics Workspace and higher-risk Splunk roles.
- Reinforce phishing-resistant workflows for privileged Splunk users until upgrades are complete.
Validation and detection
- Inventory Splunk Enterprise versions and confirm whether any are below fixed releases.
- Confirm whether Analytics Workspace is enabled or used in affected Splunk instances.
- Review role assignments for privileged users who could be targeted.
- Check Splunk logs for unusual risky SPL command activity by authenticated users.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-43566 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N2.15.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.