Improper Access Control in Field Extraction Management in Splunk Enterprise
What fixes it
- 10.4.4Splunk EnterpriseCVE List
- 10.2.8Splunk EnterpriseCVE List
- 10.0.11Splunk EnterpriseCVE List
- 9.4.16Splunk EnterpriseCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could move field extractions or field transformations to apps for which the user does not have read access. The vulnerability is possible because the Representational State Transfer (REST) API does not validate destination app access before it processes field extraction and field transformation move operations. For more information see Use the Field extractions page (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.6/use-the-settings-pages-for-field-extractions-in-splunk-web/use-the-field-extractions-page) and 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) in the Splunk documentation.
Text from CVE List
Affected versions 4
- Splunk Enterpriseaffected: 10.4 before 10.4.4CVE List
- Splunk Enterpriseaffected: 10.2 before 10.2.8CVE List
- Splunk Enterpriseaffected: 10.0 before 10.0.11CVE List
- Splunk Enterpriseaffected: 9.4 before 9.4.16CVE List