Splunk Enterprise 6.6.x, when configured to run as root but drop privileges to a specific non-root account, allows local users to gain privileges by leveraging access to that non-root account to modify $SPLUNK_HOME/etc/splunk-launch.conf and insert Trojan horse programs into $SPLUNK_HOME/bin, because the non-root setup instructions state that chown should be run across all of $SPLUNK_HOME to give non-root access.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/101664 | Third Party Advisory VDB Entry |
https://korelogic.com/Resources/Advisories/KL-001-2017-022.txt | Exploit Third Party Advisory |
https://www.splunk.com/view/SP-CAAAP3M | Vendor Advisory |
http://www.securityfocus.com/bid/101664 | Third Party Advisory VDB Entry |
https://korelogic.com/Resources/Advisories/KL-001-2017-022.txt | Exploit Third Party Advisory |
https://www.splunk.com/view/SP-CAAAP3M | Vendor Advisory |
Configurations
History
21 Nov 2024, 03:19
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securityfocus.com/bid/101664 - Third Party Advisory, VDB Entry | |
References | () https://korelogic.com/Resources/Advisories/KL-001-2017-022.txt - Exploit, Third Party Advisory | |
References | () https://www.splunk.com/view/SP-CAAAP3M - Vendor Advisory |
Information
Published : 2018-10-19 08:29
Updated : 2024-11-21 03:19
NVD link : CVE-2017-18348
Mitre link : CVE-2017-18348
CVE.ORG link : CVE-2017-18348
JSON object : View
Products Affected
splunk
- splunk
CWE
CWE-732
Incorrect Permission Assignment for Critical Resource