Sensitive Information Disclosure through the Saved Searches REST API 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, a user who does not hold the "admin" or "power" Splunk roles could view credentials configured for email notifications in a saved search shared with that user. The vulnerability is possible when email notifications use authentication credentials because the Saved Searches Representational State Transfer (REST) API returns those credentials in clear text. For more information see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.6/search-endpoints/search-endpoint-descriptions), Manage knowledge object permissions (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.6/get-started-with-knowledge-objects/manage-knowledge-object-permissions), and Email notification action (https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/10.6/configure-alert-actions/email-notification-action) in the Splunk documentation.
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