Synopsis
During the development of a detection plugin for a previous HP VTS vulnerability, one of our engineers discovered an additional issue that allows an unauthenticated attacker to delete arbitrary files on the VTS server. This was tested on Performance Center Virtual Table Server, a component of LoadRunner VTS 12.50 running on a 32-bit Windows 2008 Server host. The vulnerability was found in [HP_VTS_INSTALL_DIR]\web\admin\data.js, which is a dispatcher to handle an HTTP request. The 'f' variable is intended to hold parameters passed in the URL query string (f = querystring.parse(a)) or the POST body (f = c.body). When the user uploads a file with a POST request to url /data/import_csv and body containing "Content-Disposition: form-data; name=fileToUpload", the "path" parameter (f.path) is set to [HP_VTS_INSTALL_DIR]\web\admin\Web\file\(some_randomly_generated_file_name). This is the location where the uploaded file is put into. When VTS finishes processing the file specified in f.path, it tries to delete it.
Solution
HP has released an upgrade for Performance Center (version 12.53) to correct this issue. Please consult the vendor advisory for details.
Additional References
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c05157423http://www.zerodayinitiative.com/advisories/ZDI-16-364/
Disclosure Timeline
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]