Adobe Connect v9.6.1 - CSRF Token Web Vulnerabilit

From Lawrence Amer, 2 Months ago, written in Plain Text, viewed 288 times.
URL https://secploit.com/view/fd23208e Embed
Download Paste or View Raw
  1. Document Title:
  2. ===============
  3. Adobe Connect v9.6.1 - CSRF Token Web Vulnerability
  4.  
  5.  
  6. References (Source):
  7. ====================
  8. https://www.vulnerability-lab.com/get_content.php?id=2086
  9.  
  10.  
  11. Release Date:
  12. =============
  13. 2017-08-31
  14.  
  15.  
  16. Vulnerability Laboratory ID (VL-ID):
  17. ====================================
  18. 2086
  19.  
  20.  
  21. Common Vulnerability Scoring System:
  22. ====================================
  23. 2.8
  24.  
  25.  
  26. Vulnerability Class:
  27. ====================
  28. Cross Site Request Forgery
  29.  
  30.  
  31. Product & Service Introduction:
  32. ===============================
  33. Whether it is a smartphone or tablet app, a game, a video, a digital magazine, a website, or an online experience,
  34. chances are that it was touched by Adobe technology. Our tools and services enable our customers to create
  35. groundbreaking digital content, deploy it across media and devices, and then continually measure and optimize it
  36. based on user data. By providing complete solutions that combine digital media creation with data-driven marketing,
  37. we help businesses improve their communications, strengthen their brands, and ultimately achieve greater business success.
  38.  
  39. (Copy of the Vendor Homepage: http://www.adobe.com/aboutadobe/)
  40.  
  41.  
  42. Abstract Advisory Information:
  43. ==============================
  44. The vulnerability laboratory core research team discovered a csrf token vulnerability in the official Adobe Connect v9.6.1web-application.
  45.  
  46.  
  47. Vulnerability Disclosure Timeline:
  48. ==================================
  49. 2017-05-07: Researcher Notification & Coordination (Security Researcher)
  50. 2017-05-07: Vendor Notification (Security Department)
  51. 2017-05-09: Vendor Response/Feedback (Security Department)
  52. 2017-07-19: Vendor Fix/Patch (Service Developer Team)
  53. 2017-07-19: Security Acknowledgements  (Security Department)
  54. 2017-08-31: Public Disclosure (Vulnerability Laboratory)
  55.  
  56.  
  57. Discovery Status:
  58. =================
  59. Published
  60.  
  61.  
  62. Affected Product(s):
  63. ====================
  64.  
  65. Exploitation Technique:
  66. =======================
  67. Remote
  68.  
  69.  
  70. Severity Level:
  71. ===============
  72. Medium
  73.  
  74.  
  75. Technical Details & Description:
  76. ================================
  77. Cross site Request Forgery Token Leakage Vulnerability has been discovered in the official Adobe Connect Application.
  78.  
  79. the vulnerable module `common/scripts/JavaScriptServlet` allows remote attackers to steal the current OWASP CSRF
  80. Token which is already used in OWASP Guard Token Validation , the component it's self is placed in Public Access mode
  81. with current Authentication , mis configuration issue .
  82.  
  83. due to investigation , discovered that the body of script `common/scripts/JavaScriptServlet`, in some cases allows attacker
  84. to inject other token from trusted domains related to adobe connect .
  85.  
  86. Vulnerable Module(s):
  87. [+] common/scripts/JavaScriptServlet
  88.  
  89. Vulnerable Function(s):
  90. [+] injectTokens
  91. [+] OWASP_CSRFTOKEN
  92.  
  93.  
  94. Proof of Concept (PoC):
  95. =======================
  96. The csrf vulnerability can be exploited by remote attackers without privileged user account and with low or medium user interaction.
  97. For security demonstration or to reproduce follow the provided information and steps below to continue.
  98.  
  99. Usage of the html payload code allows an attacker to inject an own token.
  100. The exploitation is possible by usage of the html poc code via a trusted domain.
  101.  
  102. <html>
  103. [removed][removed]
  104. <body>
  105. [removed]
  106.  
  107. function injectTokens(tokenName, tokenValue) {
  108. /** obtain reference to page tokens if enabled **/
  109. var pageTokens = {};
  110.  
  111.     if(false == true) {
  112.         pageTokens = requestPageTokens();
  113.     }
  114.  
  115.     /** iterate over all elements and injection token **/
  116.     var all = document.all ? document.all : document.getElementsByTagName('*');
  117.     var len = all.length;
  118.  
  119.     for(var i=0; i<len xss=removed xss=removed xss=removed xss=removed xss=removed>
  120. &lt;/html&gt;
  121.  
  122.  
  123. Security Risk:
  124. ==============
  125. The security risk of the vulnerability in the adobe connect web-application is estimated as low (CVSS 2.8).
  126.  
  127.  
  128. Credits & Authors:
  129. ==================
  130. Lawrence Amer [zeroattck@gmail.com] - https://www.vulnerability-lab.com/show.php?user=Lawrence+Amer
  131.  
  132.  
  133. Disclaimer & Information:
  134. =========================
  135. The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed or
  136. implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable in any
  137. case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability Labs or its
  138. suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability mainly for incidental
  139. or consequential damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any licenses, policies, deface
  140. websites, hack into databases or trade with stolen data. We have no need for criminal activities or membership requests. We do not publish advisories
  141. or vulnerabilities of religious-, militant- and racist- hacker/analyst/researcher groups or individuals. We do not publish trade researcher mails,
  142. phone numbers, conversations or anything else to journalists, investigative authorities or private individuals.
  143.  
  144. Domains:    www.vulnerability-lab.com  - www.vulnerability-db.com     - www.evolution-sec.com
  145. Programs:   vulnerability-lab.com/submit.php  - vulnerability-lab.com/list-of-bug-bounty-programs.php  - vulnerability-lab.com/register.php
  146. Feeds:     vulnerability-lab.com/rss/rss.php  - vulnerability-lab.com/rss/rss_upcoming.php    - vulnerability-lab.com/rss/rss_news.php
  147. Social:     twitter.com/vuln_lab  - facebook.com/VulnerabilityLab     - youtube.com/user/vulnerability0lab
  148.  
  149. Any modified copy or reproduction, including partially usages, of this file, resources or information requires authorization from Vulnerability Laboratory.
  150. Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
  151. Vulnerability Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website is trademark
  152. of vulnerability-lab team & the specific authors or managers. To record, list, modify, use or edit our material contact (admin@) to get an ask permission.
  153.  
  154.         Copyright © 2017 | Vulnerability Laboratory - [Evolution Security GmbH]™
  155.  
  156.  
  157.  

Reply to "Adobe Connect v9.6.1 - CSRF Token Web Vulnerabilit"

Here you can reply to the paste above