LiveZilla Cross Site Scripting

2013-11-29T00:00:00
ID PACKETSTORM:124222
Type packetstorm
Reporter Curesec Research Team
Modified 2013-11-29T00:00:00

Description

                                        
                                            `Security Advisory - Curesec Research Team  
=========================================  
  
1. Introduction  
----------------  
  
Advisory ID: Cure-2013-1006  
Advisory URL: https://www.curesec.com/  
Affected Product: Prior 5.1.1.0  
Fixed Version: 5.1.1.0  
Vendor Contact: support@livezilla.net  
Vulnerability Type: Cross Site Scripting  
Remote Exploitable: Yes  
CVE: CVE-2013-6224  
Credentials: crt@curesec.com  
Reported to Vendor: 18.10.2013  
Disclosed to Public: 28.11.2013  
Release mode: Coordinated release  
  
2. Vulnerability Description  
----------------------------  
  
Various components of the LiveZilla application are vulnerable to cross  
site scripting.  
  
An attacker can hijack an operator with cross site scripting. For  
example his cookie containing parts of the login information can be  
retrieved by the attacker that he can later use to login into the  
administrator website without entering username and password. When the  
attacker enters the script code as the name before connecting and  
calling the administrator the cross site scripting vulnerability is  
triggered.  
The script code will be executed at the administrators chat website.  
  
Example XSS:  
'>><img src="foo" onerror="alert('Curesec XSS');"></img>  
  
An attacker is also able to write HTML and script code into the admins  
visitor information panel, this allows to completely modify the website  
the administrator is viewing and conduct phishing attacks.  
Another Cross Site Scripting vulnerability exists in the view archive  
section of the windows application.  
An attacker can start a chat session that the admin has to accept then  
he can send HTML and script code instead of a text message.  
When the administrator later clicks into the archive section the HTML  
and script code will be executed.  
  
5. Report Timeline  
------------------  
18.10.2013 Informed Vendor about Issue  
21.10.2013 Vendor acknowledged vulnerability. Patch is in work  
21.11.2013 Vendor published new version  
28.11.2013 Disclose to public  
  
  
`