Lucene search
K

Kaseya 6.2 Cross Site Scripting

🗓️ 01 Dec 2012 00:00:00Reported by CartelType 
packetstorm
 packetstorm
🔗 packetstormsecurity.com👁 43 Views

Persistent XSS Injection in Kaseya 6.2 via TempPath registry ke

Code
`--------------------------------------------------------------------------------------------------  
REDACTED REDACTED REDACTED REDACTED REDACTED REDACTED REDACTED  
REDACTED REDACTED REDACTED REDACTED  
ADVISORY ADVISORY ADVISORY ADVISORY ADVISORY ADVISORY ADVISORY  
ADVISORY ADVISORY ADVISORY ADVISORY  
--------------------------------------------------------------------------------------------------  
  
RA005: Persistent XSS Injection Vulnerability in Kaseya 6.2  
  
Background  
----------  
  
At Kiwicon 6 in my talk "Managed Service Pwnage", I demonstrated  
trivial flaws in Kaseya, ManageEngine and  
N-Central that could all be used to gain admin access. In accordance  
with responsible disclosure  
policy, no exploit code was released.  
  
The intention of these demonstrations was to get the MSP industry as a  
whole to wake up and take  
security seriously. It's evident from my cursory research that nobody  
in this industry does, as  
none of the flaws demonstrated would have been present.  
  
RA005-1: Persistent XSS Injection via TempPath Variable in Kaseya Agent  
--------------------------------------------------------------------------------  
  
A persistent XSS injection vulnerability was discovered in Kaseya  
using the Kaseya Agent as an injection vector.  
Specifically, it was found that the contents of the TempPath registry  
key was posted directly to the server  
with no validation. Furthermore, when displaying the value, no url  
encoding was performed.  
  
Steps to reproduce:  
1. Install the Kaseya Agent on a test computer.  
2. Stop the Kaseya Agent service.  
3. Setting the TempPath registry key to c:\kw<script>alert('xss')</script>orking  
4. Restart the Kaseya Agent and allow it to log in.  
5. Mouseover the agent's icon in the kaseya console.  
6. Observe the 'xss' popup.  
  
  
Timeline  
--------  
  
September 2012: Vulnerability discovered.  
November 17, 2012: Vulnerability demonstrated publically at Kiwicon 6.  
Details of vulnerability confidentially disclosed  
to Kaseya representative present.  
November 19, 2012: Kaseya releases HotFix 2690: "Optimize script  
injection handling in agent working folder path".  
November 20, 2012: Script injection flaw confirmed fixed.  
December 1, 2012: Advisory posted to full-disclosure, as well as  
published on the web at the following URL:  
  
http://www.redacted.co.nz/a/9b44949b9cfecbbefaa06dfdd3a48d5c9949989f1ca67d007163ed7cf7df8104  
  
  
Suggested Reading  
-----------------  
  
For the Kaseya Dev Team :-)  
  
OWASP Top Ten: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project  
Web App Hackers Handbook 2nd Edition: http://mdsec.net/wahh/  
  
  
About Kaseya  
------------  
  
from Wikipedia:  
  
Kaseya is an international company that produces remote-management  
software for the IT industry.  
It develops and sells commercial software to remotely manage and  
monitor computers running Windows,  
OSX, and Linux operating systems.  
  
  
About REDACTED  
--------------  
  
;)  
  
  
`

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation