Security readout for executives and security teams
Plain-English summary
This vulnerability lets a browser-based Splunk search request bypass safeguards around risky SPL commands. It matters because successful abuse could expose or alter data in Splunk. The sources say it requires a higher-privileged user to initiate a request in their browser and only affects deployments with Splunk Web enabled.
Executive priority
Prioritize remediation for internet-accessible or broadly reachable Splunk Web deployments, especially where privileged users regularly use the console. The issue is high severity because Splunk often centralizes sensitive operational and security data.
Technical view
CVE-2023-22935 is a CWE-20 input validation issue in Splunk Enterprise below 8.1.13, 8.2.10, and 9.0.4. The display.page.search.patterns.sensitivity search parameter can bypass SPL safeguards for risky commands. CVSS is 8.1 with high confidentiality and integrity impact, no availability impact, and user interaction required.
Likely exposure
Primary exposure is Splunk Enterprise 8.1, 8.2, or 9.0 deployments below the fixed releases with Splunk Web enabled. The source bundle also lists Splunk Cloud Platform, but provides no version detail; validate Cloud exposure through Splunk guidance.
Exploitation context
The bundle does not cite active exploitation, and CISA KEV status is false. Abuse requires a higher-privileged user to initiate a request in their browser, which makes phishing or browser-based request manipulation a plausible context, but the sources do not provide exploit evidence.
Researcher notes
Key constraints are important: Splunk Web must be enabled, user interaction is required, and the initiating browser belongs to a higher-privileged user. The public bundle does not establish active exploitation or provide detailed Splunk Cloud version impact.
Mitigation direction
- Upgrade Splunk Enterprise to 8.1.13, 8.2.10, 9.0.4, or later.
- Check Splunk advisory SVD-2023-0205 for product-specific guidance.
- Limit Splunk Web access to trusted users and networks.
- Review privileged Splunk user exposure to browser-based attack paths.
- For Splunk Cloud Platform, confirm remediation status with Splunk guidance.
Validation and detection
- Inventory Splunk Enterprise versions across all environments.
- Confirm whether Splunk Web is enabled on each instance.
- Compare versions against 8.1.13, 8.2.10, and 9.0.4 thresholds.
- Review search activity for unexpected use of the named parameter.
- Confirm Splunk Cloud Platform status with Splunk support or advisory data.
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-2023-22935 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://advisory.splunk.com/advisories/SVD-2023-0205CVE reference
- https://research.splunk.com/application/ee69374a-d27e-4136-adac-956a96ff60fdCVE 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.