||The RPC client implementation in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly allocate memory during the parsing of responses, which allows remote RPC servers and man-in-the-middle attackers to execute arbitrary code via a malformed response, aka "RPC Memory Corruption Vulnerability."
Microsoft Windows Server 2003 Service Pack 2
Microsoft Windows XP Service Pack 3
Microsoft Windows XP Service Pack 2 x64 (64-bit)
|Base: ||9.3 (as of 16-09-2010 - 13:39)|
Leverage Executable Code in Non-Executable Files
An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality.
The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
Manipulating User-Controlled Variables
This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An attacker can override environment variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the attacker can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
|impact||Remote Code Execution |
|title||Vulnerability in Remote Procedure Call Could Allow Remote Code Execution |
|NASL family||Windows : Microsoft Bulletins |
|NASL id||SMB_NT_MS10-066.NASL |
|description||The RPC client implementation on the remote host has an unspecified memory corruption vulnerability. A specially crafted RPC response to a client-initiated RPC request can result in arbitrary code execution.
A malicious RPC server could exploit this to take complete control of the host. |
|last seen||2019-02-21 |
|plugin id||49224 |
|title||MS10-066: Vulnerability in Remote Procedure Call Could Allow Remote Code Execution (982802) |
|name||Dragos Prisaca |
|organization||Symantec Corporation |
|comment||Microsoft Windows XP (x86) SP3 is installed |
|comment||Microsoft Windows XP x64 Edition SP2 is installed |
|comment||Microsoft Windows Server 2003 SP2 (x64) is installed |
|comment||Microsoft Windows Server 2003 SP2 (x86) is installed |
|comment||Microsoft Windows Server 2003 (ia64) SP2 is installed |
|description||The RPC client implementation in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly allocate memory during the parsing of responses, which allows remote RPC servers and man-in-the-middle attackers to execute arbitrary code via a malformed response, aka "RPC Memory Corruption Vulnerability." |
|title||RPC Memory Corruption Vulnerability |
|Last major update
||18-07-2011 - 22:38
||15-09-2010 - 15:00
||26-02-2019 - 09:04