Denial of Service (DoS) through Multiple LDAP Bind Requests in Splunk Enterprise
Splunk Enterprise · Splunk Enterprise Cloud
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Enterprise Cloud |
|
Splunk Enterprise · Splunk Enterprise Cloud
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Enterprise Cloud |
|
| No fix yet |
In Splunk Enterprise versions below 10.0.1, 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.108, 9.3.2408.118 and 9.2.2406.123, a user who holds a role that contains the high-privilege capability `change_authentication`, could send multiple LDAP bind requests to a specific internal endpoint, resulting in high server CPU usage, which could potentially lead to a denial of service (DoS) until the Splunk Enterprise instance is restarted. See https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities and https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/use-ldap-as-an-authentication-scheme/configure-ldap-with-splunk-web#cfe47e31_007f_460d_8b3d_8505ffc3f0dd__Configure_LDAP_with_Splunk_Web for more information.
From the CVE record · cisco
Affected Splunk Enterprise and Splunk Cloud Platform versions can experience high CPU usage when a user sends multiple LDAP bind requests to a specific internal endpoint. The user must hold a role with the high-privilege `change_authentication` capability; the requests could cause a denial of service until the Splunk Enterprise instance is restarted.
Teams running Splunk Enterprise below 10.0.1, 9.4.4, 9.3.6, or 9.2.8, or Splunk Cloud Platform below 9.3.2411.108, 9.3.2408.118, or 9.2.2406.123 should check their deployments.