Microsoft Fitbie Service - Multiple Cross Site Vulnerabilities

Document Title:
===============
Microsoft Fitbie Service - Multiple Cross Site Vulnerabilities


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


Release Date:
=============
2012-06-16


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


Common Vulnerability Scoring System:
====================================
2.3


Product & Service Introduction:
===============================
Official Microsoft (msn) Fitbie service web application.

URL: http://fitbie.msn.com/


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research team discovered multiple client side Web Vulnerabilities in Microsofts Fitbie web application service.


Vulnerability Disclosure Timeline:
==================================
2012-05-13:	Researcher Notification & Coordination
2012-05-15:	Vendor Notification
2012-05-16:	Vendor Response/Feedback
2012-06-15:	Vendor Fix/Patch
2012-06-17:	Public or Non-Public Disclosure


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


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


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


Technical Details & Description:
================================
Multiple non-persistent cross site scripting vulnerabilities are detected in Microsofts Fitbie web service application.
The vulnerability allows remote attackers to hijack website customer, moderator & admin sessions with medium or high 
required user inter action or local low privileged user account and low user inter action. Successful exploitation 
can result in account steal, phishing & client-side content request manipulation. Exploitation requires low user inter action.
The first vulnerability is located in the newsletter module with the vulnerable bound parameters mail & callback.
The second vulnerability is located in the destination module with the vulnerable bound parameters memvers profile name.

Vulnerable Module(s):

				[+] Newsletter - Mail & Callback
				[+] Destination - Member Profile


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

Review: EMail

<div class="wrapper">
      <input name="email" id="edit-email" value=""><CLIENT SIDE SCRIPT CODE EXECUTION;) <" type="hidden">
      <div class="form-checkboxes"><div class="form-item" id="edit-selectedNewsletters-2547-wrapper">


Review: callback

<input name="op" id="edit-submit" value="" src="/sites/all/themes/fitlife/images/newsletter_submit.png" 
onclick="return validateCheckBox();" class="form-submit" type="submit">
<a class="nothanks" href="/"><[CLIENT SIDE SCRIPT CODE EXECUTION]' <"="" title="No Thanks"><
img src="/sites/all/themes/fitlife/images/btn_newsletter_cancel.png" width="100" border="0" alt="No Thanks"></a>  
    </div><!--/wrapper-->
  </div><!--/newsletter-thankyou-->


PoC:
https://mc.fitbie.msn.com/newsletter/thankyou?callback=%22[CLIENT SIDE SCRIPT CODE EXECUTION]%3C&[email protected]

... or

https://mc.fitbie.msn.com/newsletter/thankyou?callback=TEST%3C&email=%22[CLIENT SIDE SCRIPT CODE EXECUTION]+%3C

... &


Note: The last issue is maybe also located in the profile user listing. Need to be checked be authorized persons.

https://fitbie.msn.com/register/thankyou?destination="[CLIENT SIDE SCRIPT CODE EXECUTION]+%3C  after first inject


Solution - Fix & Patch:
=======================
The vulnerability can be patched by parsing the input of the callback and email value.
It is also important to patch the location where the context is getting executed (output website).


Security Risk:
==============
The security risk of the client side cross site vulnerabilities are low(+)|medium(-).


Credits & Authors:
==================
Vulnerability Laboratory [Research Team]   -    Ibrahim El-Sayed [the storm] ([email protected])


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