[NT] Windows RPC Service DoS (SPIKE)

From: support@securiteam.com
Date: 10/19/02

From: support@securiteam.com
To: list@securiteam.com
Date: 19 Oct 2002 00:25:38 +0200

The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

When was the last time you checked your server's security?
How about a monthly report?
http://www.AutomatedScanning.com - Know that you're safe.
- - - - - - - - -

  Windows RPC Service DoS (SPIKE)


A security vulnerability in Windows's RPC implementaiton allows remote
attackers to cause it to no longer respond to legitimate requests by
sending it a malformed request. This effectivily allows a remote attacker
to cause a denial of service attack against the Windows operating system.


Vulnerable systems:
 * Windows 2000 SP1-SP3

Remote Windows 2000 machines with port TCP 135 open to the Internet can be
disabled without authentication of any kind. Other versions of Windows may
also be vulnerable.

Technical details:
The vulnerability itself is within the DCE-RPC stack of Windows 2000 and
related OS's. This vulnerability allows anyone who can connect to port 135
TCP to disable the RPC service. Disabling the RPC service causes the
machine to stop responding to new RPC requests, disabling almost all

This is a Denial of Service via a null pointer dereference, and not
exploitable to gain permissions on the remote machine. A proof of concept
is available at <http://www.immunitysec.com/vulnerabilities/>

This proof of concept Linux executable is derived from SPIKE 2.7 source
code. Simply running SPIKE 2.7's msrpcfuzz is also known to replicate this

Block port tcp/135 from network connections. There are also configuration
changes that can make you immune to this attack, but these are not
completely known at this time.


The information has been provided by <mailto:dave@immunitysec.com> Dave


This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com


The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #61
    ... Cisco 12000 Series Internet Router Denial Of Service Vulnerability ... Microsoft Windows 2000 RunAs Service Named Pipe Hijacking... ... Reach the LARGEST audience of security professionals with SecurityFocus ...
  • SecurityFocus Microsoft Newsletter #176
    ... MICROSOFT VULNERABILITY SUMMARY ... Microsoft Windows XP HCP URI Handler Arbitrary Command Execu... ... PHPNuke Category Parameter SQL Injection Vulnerability ... Microsoft Baseline Security Analyzer Vulnerability Identific... ...
  • SecurityFocus Microsoft Newsletter #242
    ... MICROSOFT VULNERABILITY SUMMARY ... PostNuke Blocks Module Directory Traversal Vulnerability ... Groove Networks Groove Virtual Office COM Object Security By... ... The Microsoft Windows IPV6 TCP/IP stack is prone to a "loopback" condition initiated by sending a TCP packet with the "SYN" flag set and the source address and port spoofed to equal the destination source and port. ...
  • [NT] Korean Input Method Editor Privileges Elevation (MS06-009)
    ... Get your security news from a reliable source. ... vulnerability exists in the Windows and Office Korean Input Method Editor ... Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service ... If Remote Desktop is manually enabled, ...
  • Re: SSL 2.0
    ... this is the classic tradeoff between compatibility and security. ... by default from Windows 2000 Server to Windows 2003 Server. ... may look at the instructions for disabling SSL3 and SSL3.5 and say ...