Home
» Security vulnerabilities
» CVE-2023-32716
In Splunk Enterprise versions below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform versions below 9.0.2303.100, an attacker can exploit a vulnerability in the {{dump}} SPL command to cause a denial of service by crashing the Splunk daemon.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2023-32716
Conclusion & alert: CVE-2023-32716 is rated Moderate Risk (42/100) : CVSS Medium severity, with low exploitation likelihood (EPSS 0.62%). Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2023-32716
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.39%
0.62%
+0.23%
2
2026-06-14
0.25%
0.39%
+0.14%
3
2026-06-05
—
0.25%
—
Full EPSS history
(13 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2023-32716
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
6.5
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8
3.6
[email protected]
6.5
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8
3.6
[email protected]
Weakness enumeration for CVE-2023-32716
Affected software / configurations for CVE-2023-32716
Vendor
Product
Version
Raw CPE
splunk
splunk
>= 8.1.0, < 8.1.14
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk
splunk
>= 8.2.0, < 8.2.11
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk
splunk
>= 9.0.0, < 9.0.5
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk
splunk_cloud_platform
< 9.0.2303.100
cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*
References for CVE-2023-32716
cvelogic
Threat Intelligence