Blind Server Side Request Forgery (SSRF) through Distributed Search Peers in Splunk Enterprise
Splunk Enterprise · Splunk Cloud Platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
Splunk Enterprise · Splunk Cloud Platform
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise |
| No fix yet |
| Splunk Splunk Cloud Platform |
|
| No fix yet |
In Splunk Enterprise versions below 10.0.1, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.4, 10.0.2503.7, and 9.3.2411.116, a user who holds a role that contains the high privilege capability `change_authentication` could enumerate internal IP addresses and network ports when adding new search peers to a Splunk search head in a distributed environment.
From the CVE record · cisco
Affected Splunk Enterprise and Splunk Cloud Platform versions allow a user with a role containing the high-privilege `change_authentication` capability to enumerate internal IP addresses and network ports. This can occur when the user adds new search peers to a Splunk search head in a distributed environment.
Teams running Splunk Enterprise below 10.0.1, 9.4.6, 9.3.8, or 9.2.10, or Splunk Cloud Platform below 10.1.2507.4, 10.0.2503.7, or 9.3.2411.116, should check their deployments.