CVE-2017-5607 : Detail

CVE-2017-5607

3.5
/
Low
A01-Broken Access Control
1.94%V3
Network
2017-04-10
13h00 +00:00
2018-10-09
16h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

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.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 3.5 LOW CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers).

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker is authorized with (i.e. requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

 [email protected]
V2 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 41779

Publication date : 2017-03-30 22h00 +00:00
Author : hyp3rlinx
EDB Verified : Yes

[+] Credits: John Page AKA hyp3rlinx [+] Website: hyp3rlinx.altervista.org [+] Source: http://hyp3rlinx.altervista.org/advisories/SPLUNK-ENTERPRISE-INFORMATION-THEFT.txt [+] ISR: ApparitionSec Vendor: =============== www.splunk.com Product: ================== Splunk Enterprise Splunk provides the leading platform for Operational Intelligence. Customers use Splunk to search, monitor, analyze and visualize machine data. Splunk Enterprise, collects and analyzes high volumes of machine-generated data. Vulnerability Type: ================================== Javascript (JSON) Information Theft CVE Reference: ============== CVE-2017-5607 Security Issue: ================ Attackers can siphon information from Splunk Enterprise if an authenticated Splunk user visits a malicious webpage. Some useful data gained is the currently logged in username and if remote user setting is enabled. After, the username can be use to Phish or Brute Force Splunk Enterprise login. Additional information stolen may aid in furthering attacks. Root cause is the global Window JS variable assignment of config?autoload=1 '$C'. e.g. window.$C = {"BUILD_NUMBER": 207789, "SPLUNKD_PATH"... etc... } To steal information we simply can define a function to be called when the '$C' JS property is "set" on webpage, for example. Object.defineProperty( Object.prototype, "$C", { set:function(val){... The Object prototype is a Object that every other object inherits from in JavaScript, if we create a setter on the name of our target in this case "$C", we can get/steal the value of this data, in this case it is very easy as it is assigned to global Window namespace. Affected Splunk Enterprise versions: 6.5.x before 6.5.3 6.4.x before 6.4.6 6.3.x before 6.3.10 6.2.x before 6.2.13.1 6.1.x before 6.1.13 6.0.x before 6.0.14 5.0.x before 5.0.18 and Splunk Light before 6.5.2 Vulnerability could allow a remote attacker to obtain logged-in username and Splunk version-related information via JavaScript. References: ============= https://www.splunk.com/view/SP-CAAAPZ3 https://www.splunk.com/view/SP-CAAAPZ3#InformationLeakageviaJavaScriptCVE20175607 Exploit/POC: ============= Reproduction: 1) Log into Splunk 2) place the below Javascript in webpage on another server. "Splunk-Data-Theft.html" <script> Object.defineProperty( Object.prototype, "$C", { set:function(val){ //prompt("Splunk Timed out:\nPlease Login to Splunk\nUsername: "+val.USERNAME, "Password") for(var i in val){ alert(""+i+" "+val[i]); } } }); </script> <script src="https://VICTIM-IP:8000/en-US/config?autoload=1"></script> 3) Visit the server hosting the "Splunk-Data-Theft.html" webpage, grab current authenticated user 4) Phish or brute force the application. Video POC URL: =============== https://vimeo.com/210634562 Network Access: =============== Remote Impact: ======================= Information Disclosure Severity: ========= Medium Disclosure Timeline: =================================================== Vendor Notification: November 30, 2016 Vendor Acknowledgement: December 2, 2016 Vendor Release Splunk 6.5.3 / Patch : March 30, 2017 March 31, 2017 : Public Disclosure [+] Disclaimer The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise. Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information or exploits by the author or elsewhere. All content (c).

Products Mentioned

Configuraton 0

Splunk>>Splunk >> Version To (including) 6.5.1

Configuraton 0

Splunk>>Splunk >> Version From (including) 5.0.0 To (excluding) 5.0.18

Splunk>>Splunk >> Version From (including) 6.0.0 To (excluding) 6.0.14

Splunk>>Splunk >> Version From (including) 6.1.0 To (excluding) 6.1.13

Splunk>>Splunk >> Version From (including) 6.2.0 To (excluding) 6.2.13.1

Splunk>>Splunk >> Version From (including) 6.3.0 To (excluding) 6.3.10

Splunk>>Splunk >> Version From (including) 6.4.0 To (excluding) 6.4.6

Splunk>>Splunk >> Version From (including) 6.5.0 To (excluding) 6.5.3

References

http://www.securitytracker.com/id/1038170
Tags : vdb-entry, x_refsource_SECTRACK
https://www.exploit-db.com/exploits/41779/
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.securityfocus.com/bid/97286
Tags : vdb-entry, x_refsource_BID
http://seclists.org/fulldisclosure/2017/Mar/89
Tags : mailing-list, x_refsource_FULLDISC
http://www.securityfocus.com/bid/97265
Tags : vdb-entry, x_refsource_BID