Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] Dell KACE K2000 System Deployment Appliance Multiple Reflected XSS



Dell KACE K2000 System Deployment Appliance contains a flaw that allows a remote cross-site scripting (XSS) attack. This flaw exists because the application does not validate input to the 'log' parameter of the /settings_logs facility and the 'network_test_name' parameter of the /support_troubleshooting facility before returning it to the user. This may allow a user to create a specially crafted URL that would execute arbitrary script code in a user's browser within the trust relationship between their browser and the server.


As of 2011-10-13, CERT/CC indicated that Dell was preparing to release an update. Unfortunately, the original KB posted by Dell has since been removed from the site, so it is unclear if a solution was published.

Proof of Concept


Disclosure Timeline

2011-05-03 - Vulnerability reported to CERT/CC via their online submission form, assigned VU #135606
2011-06-09 - CERT/CC acknowledges and says they're contacting Dell
2011-08-15 - Asked CERT/CC for an update
2011-10-13 - CERT/CC responds saying Dell is prepared to issue an update
2011-11-03 - Disclosed via CERT/CC

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]