Security readout for executives and security teams
Plain-English summary
This is a high-severity Splunk Enterprise issue where a phished user could be tricked into initiating a browser request that bypasses safeguards meant to restrict risky SPL commands. The main business concern is unauthorized access to or modification of sensitive Splunk data, not service outage.
Executive priority
Treat this as a near-term remediation item for affected Splunk Enterprise environments. Prioritize systems containing sensitive logs, security telemetry, or privileged operational data, especially where Splunk users have broad search permissions.
Technical view
CVE-2022-43565 affects Splunk Enterprise 8.1 and 8.2 below 8.1.12 and 8.2.9. The tstats command's JSON handling can bypass SPL risky-command safeguards. The CVSS 3.1 vector is network exploitable with low complexity, no privileges, required user interaction, and high confidentiality and integrity impact.
Likely exposure
Exposure is limited to Splunk Enterprise deployments on affected 8.1 or 8.2 versions. Risk is higher where users access Splunk in browsers and can be phished. The bundle does not identify Splunk Cloud or other products as affected.
Exploitation context
The source states exploitation requires phishing the victim into initiating a browser request. There is no KEV listing in the bundle, so active exploitation is not established from the provided evidence.
Researcher notes
The key weakness is input validation in tstats JSON handling, mapped to CWE-20. Public evidence in the bundle supports affected versions, impact, and phishing-based user interaction, but does not establish weaponized exploit availability or active exploitation.
Mitigation direction
- Upgrade Splunk Enterprise 8.1 deployments to 8.1.12 or later.
- Upgrade Splunk Enterprise 8.2 deployments to 8.2.9 or later.
- Review Splunk's advisory for any environment-specific guidance.
- Reinforce phishing controls for Splunk administrators and analysts.
Validation and detection
- Inventory Splunk Enterprise versions across production, staging, and admin systems.
- Confirm no affected 8.1 or 8.2 builds remain deployed.
- Review Splunk activity for unusual risky-command attempts involving tstats and JSON.
- Check whether SPL safeguard settings are enabled and monitored.
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-43565 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
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:R/S:U/C:H/I:H/A:N2.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-1105.htmlCVE reference
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.