CVE-2017-5607: Infoleak
Splunk Enterprise 5.0.x before 5.0.18, 6.0.x before 6.0.14, 6.1.x before 6.1.13, 6.2.x before 6.2.13.1, 6.3.x before 6.3.10, 6.4.x before 6.4.6, and 6.5.x before 6.5.3 and Splunk Light before 6.5.2 assigns the $C JS property to the global Window namespace, which might allow remote attackers to obtain sensitive logged-in username and version-related information via a crafted webpage.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 5.0.18 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 6.0.14 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 6.1.13 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 6.2.13.1 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 6.3.10 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 6.4.6 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 6.5.3 - Upgrade
Upgrade
Splunk Lightto a version that resolves this vulnerability.Fixed in 6.5.2
Event History
Frequently Asked Questions
What is the severity of CVE-2017-5607?
The severity of CVE-2017-5607 is classified as low with a score of 3.5.
How do I fix CVE-2017-5607?
To fix CVE-2017-5607, you should upgrade to the latest version of Splunk that is not vulnerable.
Which versions of Splunk are affected by CVE-2017-5607?
CVE-2017-5607 affects Splunk Enterprise versions before 5.0.18, 6.0.14, 6.1.13, 6.2.13.1, 6.3.10, 6.4.6, 6.5.3 and Splunk Light before 6.5.2.
What type of vulnerability is CVE-2017-5607?
CVE-2017-5607 is classified as an information theft vulnerability.
Can CVE-2017-5607 be exploited remotely?
Yes, CVE-2017-5607 can potentially be exploited by remote attackers.