Security readout for executives and security teams
Plain-English summary
CVE-2023-22938 lets any authenticated Splunk Enterprise user send email as the Splunk instance through the sendemail REST API. This is not unauthenticated system compromise, but it can support misleading internal emails or abuse of trusted Splunk identity. Fixed Enterprise versions restrict the endpoint to the local splunk-system-user account.
Executive priority
Treat as a moderate-priority hygiene fix. It is not described as actively exploited or critical, but Splunk often sits in trusted operational workflows, so unauthorized email sending can create business confusion or phishing-like risk.
Technical view
Splunk Enterprise below 8.1.13, 8.2.10, and 9.0.4 has a permissions validation failure in the sendemail REST API endpoint. The CVSS 3.1 score is 4.3, with network access, low complexity, low privileges, no user interaction, and low integrity impact. Sources classify it as CWE-285.
Likely exposure
Exposure is most likely where affected Splunk Enterprise versions are reachable by authenticated users. The bundle also lists Splunk Cloud Platform, but does not provide version-specific Cloud exposure details. Risk depends on who can authenticate to Splunk and whether Splunk email sending is trusted internally.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Abuse requires Splunk authentication and affects message integrity, not confidentiality or availability. The main concern is unauthorized email origination from a trusted Splunk instance.
Researcher notes
Evidence is limited to the CVE record and Splunk advisory reference in the bundle. The fix behavior is explicit: restrict sendemail to splunk-system-user on the local instance. Do not assume broader code execution, data access, or Cloud-specific remediation without vendor confirmation.
Mitigation direction
- Upgrade Splunk Enterprise to 8.1.13, 8.2.10, 9.0.4, or later.
- Review Splunk advisory SVD-2023-0208 for product-specific guidance.
- Restrict Splunk authentication to trusted users until fixed.
- Review Splunk Cloud guidance with the vendor if applicable.
Validation and detection
- Inventory Splunk Enterprise versions across all environments.
- Confirm no instance runs below 8.1.13, 8.2.10, or 9.0.4.
- Review role assignments for unnecessary authenticated Splunk access.
- Review mail logs for unexpected Splunk-originated messages.
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-285: 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-22938 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://advisory.splunk.com/advisories/SVD-2023-0208CVE 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 Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.