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.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Link | Tags |
---|---|
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 | third party advisory exploit |