Avira Service - Unvalidated CSRF Token Account Hijacking

Document Title:
===============
Avira Service - Unvalidated CSRF Token Account Hijacking


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

View: https://www.youtube.com/watch?v=lJR8Hv5JnOI



Release Date:
=============
2014-08-28


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


Common Vulnerability Scoring System:
====================================
3.1


Vulnerability Disclosure Timeline:
==================================
2014-08-21:	Researcher Notification & Coordination (Mazen Gamal)
2014-08-22:	Vendor Notification (Avira Security Team)
2014-08-22:	Vendor Response/Feedback (Avira Security Team)
2014-08-22:	Vendor Fix/Patch Notification (Avira Developer Team)
2014-08-28:	Public Disclosure (Vulnerability Laboratory)


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


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


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


Technical Details & Description:
================================
The video shows the live video demonstration of a reported security vulnerability to the avira company. The issue has been exploited in a video 
demonstration by Mazen Gamal an independent lab researcher. Within 6 hours the website security team was preparing a patch to fix the vulnerability.
The video explains with some easy steps how the issue has been exploited by the arab researcher.


Credits & Authors:
==================
Mazen Gamal - http://www.vulnerability-lab.com/show.php?user=Mazen%20Gamal


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:    [email protected] 	- [email protected] 	       		- [email protected]
Section:    dev.vulnerability-db.com	 	- 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
Programs:   vulnerability-lab.com/submit.php  	- vulnerability-lab.com/list-of-bug-bounty-programs.php	- vulnerability-lab.com/register/

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 
([email protected] or [email protected]) to get a permission.

				Copyright © 2014 | Vulnerability Laboratory [Evolution Security]