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.
2018-10-19T08:29:00.263
2024-11-21T03:19:54.043
Modified
CVSSv3.0: 7.0 (HIGH)
AV:L/AC:M/Au:N/C:C/I:C/A:C
3.4
10.0