LiveData Protocol Server Heap Overflow Lets Remote Users Execute Arbitrary Code
SecurityTracker Alert ID: 1017998|
SecurityTracker URL: http://securitytracker.com/id/1017998
(Links to External Site)
Updated: May 13 2008|
Original Entry Date: May 2 2007
Execution of arbitrary code via network, Root access via network|
Fix Available: Yes Vendor Confirmed: Yes |
A vulnerability was reported in LiveData Protocol Server. A remote user can execute arbitrary code on the target system.|
A remote user can connect to port 8080 and send a specially crafted request for WSDL files to trigger a heap overflow and execute arbitrary code on the target system. The code will run with System privileges.
The vendor was notified of January 2, 2007.
iDefense reported this vulnerability.
A remote user can execute arbitrary code on the target system with System level privileges.|
The vendor has issued a fixed version (500062).|
Vendor URL: www.livedata.com/ (Links to External Site)
|Underlying OS: Windows (Any)|
Source Message Contents
Subject: iDefense Security Advisory 05.02.07: LiveData Protocol Server Heap|
LiveData Protocol Server Heap Overflow Vulnerability
iDefense Security Advisory 05.02.07
May 02, 2007
LiveData is a provider of real-time data acquisition and processing
software. LiveData Protocol Server is used in SCADA environments to
record and transmit data to other control points in process control
networks. The LiveData server includes a HTTP server that offers a SOAP
interface to the product. More information is available at the vendor's
web site at the following URL.
Remote exploitation of a heap overflow vulnerability within LiveData's
Protocol Server could allow an attacker to cause the service to crash
or potentially execute arbitrary code with SYSTEM privileges.
The vulnerability specifically exists due to the the handling of
WSDL files. By supplying a specially crafted request to the service on port
8080, an attacker is able to supply a negative length value to a strncpy
This value is interpreted by strncpy as a very large positive value. As a
result, a memory access violation occurs when attempting to write data
end of the heap memory segment.
Exploitation allows an attacker to crash the LiveDataServer service or
potentially execute arbitrary code.
Arbitrary code execution would depend on overwriting heap data that is
used within a different thread. A race condition would have to exist
where the flow of execution would be diverted before the application
terminated from the memory access violation.
iDefense has confirmed the existence of this vulnerability in LiveData
Protocol Server version 5.00.045 which was the current release as of
September 13th 2006.
In order to mitigate potential exploitation, iDefense recommends
blocking access to port 8080 by using a firewall.
VI. VENDOR RESPONSE
LiveData has addressed this vulnerability with updated versions of their
software. The following versions are reported to be fixed.
RTI update 500062
Protocol Server update 500062
Maintenance Server update 500062
VII. CVE INFORMATION
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not
been assigned yet.
VIII. DISCLOSURE TIMELINE
01/02/2007 Initial vendor notification
01/03/2007 Initial vendor response
05/02/2007 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically,
please e-mail email@example.com for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct,
indirect, or consequential loss or damage arising from use of, or
reliance on, this information.
To unsubscribe, go here: