CVE-2023-32707
Published: 01 June 2023
Summary
CVE-2023-32707 is a high-severity Improper Authorization (CWE-285) vulnerability in Splunk Splunk. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below 9.0.2303.100, a privilege escalation vulnerability allows a low-privileged user holding the edit_user capability to gain administrative access through specially crafted web requests. The flaw is tracked as CVE-2023-32707 with a CVSS 3.1 score of 8.8 and is associated with CWE-285 improper authorization.
An attacker with a role that includes the edit_user capability can send crafted requests to the affected Splunk instance and escalate their privileges to full admin level, resulting in complete control over the deployment including the ability to read, modify, or delete data and configurations.
Splunk advisory SVD-2023-0602 and associated research notes recommend upgrading Splunk Enterprise to 9.0.5, 8.2.11, or 8.1.14 and Splunk Cloud Platform to 9.0.2303.100 or later to remediate the issue. The EPSS score has reached a peak of 0.8863 with a current value of 0.8268.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-36934
Vulnerability details
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100, a low-privileged user who holds a role that has the ‘edit_user’ capability assigned to it can escalate their privileges to that of the…
more
admin user by providing specially crafted web requests.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Documented procedures facilitate correct implementation and ongoing management of authorization decisions.
Periodic reviews identify and correct flaws in authorization decisions or enforcement.
The control's documentation requirement reduces improper authorization by ensuring only mission-justified actions bypass authentication.
Establishing permitted attributes and values, plus auditing changes, ensures authorization decisions are based on correctly managed policy data.
Explicitly mandates authorizing remote access types before permitting connections, directly mitigating improper authorization.
The control explicitly requires authorization of each wireless access type prior to permitting connections.
Mandating explicit authorization of mobile device connections reduces the risk of improper authorization decisions for system access.
Specifying access authorizations for each account and requiring approvals for account requests enforces proper authorization decisions.