Vulnerability Note VU#261537
Microsoft Windows RPC service vulnerable to DoS via NULL pointer dereference
The RPC service in Microsoft Windows NT 4.0, 2000, and XP can be terminated by a specially crafted RPC message. A remote attacker could cause a denial of service.
According to Microsoft Security Bulletin MS03-010, "Remote Procedure Call (RPC) is a protocol used by the Windows operating system. RPC provides an inter-process communication mechanism that allows a program running on one computer to seamlessly execute code on a remote system."
A vulnerability exists in a part of the RPC service called the RPC Endpoint Mapper. The RPC Endpoint Mapper listens for network requests (135/tcp), provides clients with port numbers for RPC services, and maintains information about RPC connections. According to a report from Immunity Security, vulnerable code in the RPC Endpoint Mapper dereferences a NULL pointer when processing a malformed RPC message.
An unauthenticated, remote attacker could cause the RPC Endpoint Mapper to terminate, denying service to legitimate users. Since the RPC Endpoint Mapper is part of the RPC service, "...exploiting this vulnerability would cause the RPC service to fail, with the attendant loss of any RPC-based services the server offers, as well as potential loss of some COM functions."
Once the RPC service has been terminated, an attacker may be able to take control over an orphaned named pipe and gain the privileges of the RPC service (Local System).
Apply the appropriate patch (Q331953) as specified in MS03-010. Microsoft notes that a patch will not be produced for Windows NT 4.0 or Windows NT 4.0 Terminal Server Edition.
The patches may cause local COM calls to fail, which could affect ASP/COM+ applications. See Microsoft Knowledgebase Article 814119 for more information.
Block or Restrict Access
Block or restrict access to the RPC Endpoint Mapper service (135/tcp) from untrusted networks such as the Internet.
If you are a vendor and your product is affected, let
|Vendor||Status||Date Notified||Date Updated|
|Microsoft Corporation||Affected||-||26 Mar 2003|
This vulnerability was publicly reported by Dave Aitel of
This document was written by Art A Manion.
18 Oct 2002
Date First Published:
26 Mar 2003
Date Last Updated:
04 Jun 2003
If you have feedback, comments, or additional information about this vulnerability, please send us email.