Sensitive Information Disclosure through the storage/passwords REST Endpoint 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 |
|
≥ 10.2.2510 · < 10.2.2510.18≥ 10.1.2507 · < 10.1.2507.24| No fix yet |
In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.3.2512.15, 10.2.2510.18, and 10.1.2507.24, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could view stored credential hashes when they access the `/servicesNS/-/-/storage/passwords` REST endpoint through the `|rest` Search Processing Language (SPL) command.<br><br>The exposure happens because the `|rest` SPL command returns the `encr_password` field in the results of the `/servicesNS/-/-/storage/passwords` REST endpoint.
From the CVE record · cisco
In affected Splunk Enterprise and Splunk Cloud Platform versions, the |rest SPL command returns stored credential hashes from the /servicesNS/-/-/storage/passwords endpoint. An authenticated, low-privileged user without the admin or power role can view those hashes by accessing the endpoint through that command.
Teams running Splunk Enterprise below 10.4.1, 10.2.5, 10.0.8, or 9.4.13, or Splunk Cloud Platform below 10.5.2605.0, 10.4.2604.6, 10.3.2512.15, 10.2.2510.18, or 10.1.2507.24 should check their deployments.