Splunk up to 6.5.2 JSON Username information disclosure

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.7	$0-$5k	0.00

Summaryinfo

A vulnerability has been found in Splunk up to 6.5.2 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component JSON Handler. Performing a manipulation results in information disclosure (Username). This vulnerability is known as CVE-2017-5607. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Splunk up to 6.5.2 (Log Management Software). This affects an unknown part of the component JSON Handler. The manipulation with an unknown input leads to a information disclosure vulnerability (Username). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on integrity.

The bug was discovered 04/01/2017. The weakness was published 03/27/2017 by John Page (hyp3rlinx) as confirmed advisory (Website). The advisory is shared at splunk.com. This vulnerability is uniquely identified as CVE-2017-5607 since 01/28/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

A public exploit has been developed by John Page (hyp3rlinx) and been published 4 days after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 97100 (Splunk Enterprise < 5.0.17 / 6.0.13 / 6.1.12 / 6.2.13 / 6.3.9 / 6.4.5 / 6.5.2 or Splunk Light < 6.5.2 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 11788 (Splunk Enterprise and Light Multiple Vulnerabilities (SP-CAAAPZ3)). The code used by the exploit is:

<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>

Upgrading to version 6.2.13.1 or 6.5.3 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (41779), Tenable (97100), SecurityFocus (BID 97265†) and SecurityTracker (ID 1038170†). Similar entry is available at VDB-96548. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Log Management Software

Name

• Splunk

Version

• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6
• 5.0.7
• 5.0.8
• 5.0.9
• 5.0.10
• 5.0.11
• 5.0.12
• 5.0.13
• 5.0.14
• 5.0.15
• 5.0.16
• 5.0.17
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11
• 6.1.12
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 6.2.11
• 6.2.12
• 6.2.13.0
• 6.3.0
• 6.3.1
• 6.3.2
• 6.3.3
• 6.3.4
• 6.3.5
• 6.3.6
• 6.3.7
• 6.3.8
• 6.3.9
• 6.4.0
• 6.4.1
• 6.4.2
• 6.4.3
• 6.4.4
• 6.4.5
• 6.5.0
• 6.5.1
• 6.5.2

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

Video

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.9
VulDB Meta Temp Score: 3.7

VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.5
NVD Vector: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Username
Class: Information disclosure / Username
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: John Page (hyp3rlinx)
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Nessus ID: 97100
Nessus Name: Splunk Enterprise < 5.0.17 / 6.0.13 / 6.1.12 / 6.2.13 / 6.3.9 / 6.4.5 / 6.5.2 or Splunk Light < 6.5.2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 100694
OpenVAS Name: Splunk Light Multiple XSS Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍

Upgrade: Splunk 6.2.13.1/6.5.3

Timelineinfo

01/28/2017 🔍
02/10/2017 +13 days 🔍
03/27/2017 +45 days 🔍
03/27/2017 +0 days 🔍
03/27/2017 +0 days 🔍
03/31/2017 +4 days 🔍
03/31/2017 +0 days 🔍
03/31/2017 +0 days 🔍
04/01/2017 +1 days 🔍
04/02/2017 +1 days 🔍
04/10/2017 +8 days 🔍
07/21/2025 +3024 days 🔍

Sourcesinfo

Advisory: splunk.com
Researcher: John Page (hyp3rlinx)
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-5607 (🔍)
GCVE (CVE): GCVE-0-2017-5607
GCVE (VulDB): GCVE-100-99165
SecurityFocus: 97265 - Splunk Enterprise CVE-2017-5607 Information Disclosure Vulnerability
OSVDB: - CVE-2017-5607 - Splunk - Information Disclosure Issue
SecurityTracker: 1038170

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 04/02/2017 13:48
Updated: 07/21/2025 02:39
Changes: 04/02/2017 13:48 (92), 08/27/2020 16:53 (6), 11/24/2022 12:45 (4), 07/21/2025 02:39 (14)
Complete: 🔍
Cache ID: 216:70A:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

Interested in the pricing of exploits?

See the underground prices here!