Document Title:
===============
Avira Analysis Web Service - SQL Injection Vulnerability


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

Public Video: http://www.youtube.com/watch?v=128cIzgt2EI


Release Date:
=============
2013-07-07


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


Common Vulnerability Scoring System:
====================================
8.5


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Core Research Team discovered a critical SQL Injection vulnerability in the Avira Analysis online service application.


Vulnerability Disclosure Timeline:
==================================
2013-05-25:    Vendor Notification (Ebrahim Hegazy)
2013-05-26:    Vendor Response/Feedback (Avira Security Team)
2013-06-31:    Vendor Fix/Patch (Avira Developer Team)
2013-07-08:    Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================
Avira
Product: Analysis - Web Application & Online Service 2013 Q2


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


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


Technical Details & Description:
================================
A remote SQL Injection web vulnerability is detected in ِ the official Avira Analysis online service application.
The vulnerability allows remote attackers to inject own sql commands to compromise the affected application dbms.

The SQL Injection vulnerability is located in the `overview` file when processing to request manipulated `uniqueid` parameter. 
By manipulation of the `uniqueid` parameter the attackers can inject own sql commands to compromise the webserver application dbms. 

When processing to bypass the filter validation by trying to use a single qoute or a double qoute to check if the parameter is vulnerable or not, 
attackers will be redirected to another page, but when the attacker is processing to request with a back-slash the context will be executed 
and new mysql errors will become visible for exploitation.

The vulnerability can be exploited by remote attackers without privileged application user account and without required user interaction. 
Successful exploitation of the sql injection vulnerability results in web application and online service dbms compromise.

Vulnerable Module(s):
				[+] en

Vulnerable File(s):
				[+] overview

Vulnerable Module(s):
				[+] uniqueid


Proof of Concept (PoC):
=======================
The remote sql injection web vulnerability can be exploited by remote attackers without privileged application user account and without 
required user interaction. For demonstration or reproduce ...

Vulnerable Service Domain:	analysis.avira.com
Vulnerable Module:		en
Vulnerable File:		overview
Vulnerable Parameter:		uniqueid


Note: When trying to use a single qoute or a double qoute to check if the parameter is vulnerable or not, you will be redirected to another page, 
but when processing to load with a back-slash new mysql errors will become visible for exploitation.


POC: 
https://analysis.avira.com/en/overview?start=0&uniqueid=1YcGIXI0qbPbpTHg7YvFEr8MG7JmkbSg\[SQL INJECTION VULNERABILITY!]


PoC Video:
http://www.youtube.com/watch?v=128cIzgt2EI


Reference(s):
https://analysis.avira.com/


Solution - Fix & Patch:
=======================
The vulnerability can be patched by a restriction and secure parse of the uniqueid parameter request.


Security Risk:
==============
The security risk of the remote sql injection web vulnerability is estimated as critical.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Ebrahim Hegazy [Zigoo] (ebrahim@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.vulnerability-lab.com/register
Contact:    admin@vulnerability-lab.com 	- support@vulnerability-lab.com 	       - research@vulnerability-lab.com
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, 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 support@vulnerability-lab.com) to get a permission.

    				   	Copyright © 2013 | Vulnerability Laboratory