Information Disclosure through the REST API and Splunk Web in Splunk Enterprise
Summary
In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could determine whether a username exists through the Representational State Transfer (REST) API or Splunk Web and lock out existing user accounts through repeated login attempts.
The vulnerabili...
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| SplunkSplunk Enterprise |
≥ 10.6, < 10.6.1→ 10.6.1 ≥ 10.4, < 10.4.5→ 10.4.5 ≥ 10.2, < 10.2.9→ 10.2.9 ≥ 10.0, < 10.0.12→ 10.0.12 ≥ 9.4, < 9.4.17→ 9.4.17 |
10.6.1 10.4.5 10.2.9 10.0.12 9.4.17 |
Original description The description as published by the source.
In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could determine whether a username exists through the Representational State Transfer (REST) API or Splunk Web and lock out existing user accounts through repeated login attempts.
The vulnerability is possible because Splunk Enterprise returns different login failure responses for locked existing user accounts and nonexistent usernames.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- web psirt@cisco.com