CVE-2017-18348

low-risk
Published 2018-10-19

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.

Do I need to act?

-
0.12% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.0/10 High
LOCAL / HIGH complexity

Affected Products (1)

Affected Vendors

Splunk

References (6)

Third Party Advisory http://www.securityfocus.com/bid/101664
Exploit https://korelogic.com/Resources/Advisories/KL-001-2017-022.txt
Vendor Advisory https://www.splunk.com/view/SP-CAAAP3M
Third Party Advisory http://www.securityfocus.com/bid/101664
Exploit https://korelogic.com/Resources/Advisories/KL-001-2017-022.txt
Vendor Advisory https://www.splunk.com/view/SP-CAAAP3M
23
/ 100
low-risk
Severity 18/34 · Moderate
Exploitability 0/34 · Minimal
Exposure 5/34 · Minimal