Information Disclosure through the REST API and Splunk Web in Splunk Enterprise
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Enterprise 10.0.12, Enterprise 10.2.9, Enterprise 10.4.5 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Splunk | Enterprise | >=10.0 <10.0.12, >=10.2 <10.2.9, >=10.4 <10.4.5, >=10.6 <10.6.1, >=9.4 <9.4.17 | 10.0.12, 10.2.9, 10.4.5, 10.6.1, 9.4.17 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Enterprise, strongest first
Embed
A live severity badge for an advisory, README or ticket