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

[R1] HPE LoadRunner libxdrutil.dll mxdr_string() Function XDR String Handling Remote Heap Buffer Overflow

Critical

Synopsis

While examining the protocol used by the LoadRunner agent to develop Nessus detection plugins for previous vulnerabilities, Tenable found a heap buffer overflow issue that may allow for remote code execution. The flaw is in the mxdr_string() function of the libxdrutil.dll library. An attacker can craft an XDR string with a very large length (i.e., 0xfffffffc), which when processed in libxdrutil.dll!mxdr_string(), the function ends up allocating 0xffffffffc + 5 = 1 byte from the heap, which causes a small buffer to be returned. Next, the function copies 0xfffffffc bytes of attacker-controlled data to the small buffer, resulting in a heap buffer overflow. Technical shared the technical debugging / crash pleasantry with ZDI.

This was tested against HPE LoadRunner 12.53.0 running on 32-bit Windows 2008 SP2. Tenable generated a Python PoC script (loadrunner_mxdr_string_heap_overflow.py) that demonstrates this issue. If you are with ZDI you have a copy. Otherwise, sorry!

Solution

HPE has released both HPE LoadRunner 12.53.0 Patch 4 and HPE Performance Center 12.53.0 Patch 4 to address this issue. They do not explicitly say it, but we assume Patch levels 1 to 3 would be vulnerable.

Disclosure Timeline

2016-06-21 - Issue discovered
2016-06-21 - Submitted to ZDI, case bmartin0014 opened
2016-07-20 - Ping ZDI for update
2016-07-20 - ZDI replies, their case load is huge, preparing for BlackHat, will get back ASAP
2016-07-29 - ZDI offers $1000 for this work
2016-07-29 - Tenable accepts
2016-07-29 - ZDI confirms
2016-11-30 - Vulnerability reported to vendor by ZDI
2017-03-07 - HP advisory posted
2017-03-09 - ZDI advisory posted

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 advisories@tenable.com