Document Title:
===============
Microsoft Yammer SN - oAuth Bypass Token Vulnerability


References:
===========
http://www.vulnerability-lab.com/get_content.php?id=1043

View: http://www.youtube.com/watch?v=SwxWNvmOsU4

Advisory:  http://www.vulnerability-lab.com/get_content.php?id=1003

Microsoft Security Response Center (MSRC) ID:  15126



Release Date:
=============
2013-08-03


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


Common Vulnerability Scoring System:
====================================
9.3


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


Exploitation Technique:
=======================
Offensiv


Severity Level:
===============
Critical


Technical Details & Description:
================================
The vulnerability has been discovered by Ateeq Khan a pakistani researcher and new core member of the vulnerability laboratory team.
The video shows how to exploit a session token vulnerability in the new microsoft yammer social network application for users, customers and ms clients.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Ateeq Khan (ateeq@evolution-sec.com)


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.evolution-sec.com
Contact:    admin@vulnerability-lab.com 	- research@vulnerability-lab.com 	       - admin@evolution-sec.com
Section:    www.vulnerability-lab.com/dev 	- forum.vulnerability-db.com 		       - magazine.vulnerability-db.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, source code, 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 (admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.

				Copyright © 2013 | Vulnerability Laboratory [Evolution Security]