This article was previously published under Q179129
Windows NT may stop responding (hang) with a STOP 0x0000000A or 0x00000019message after receiving a number of deliberately corrupted UDP packets.
This behavior occurs due to a variation of the "teardrop" attack. WindowsNT 4.0 with Service Pack 3 and the ICMP-fix is not susceptible to theoriginal form of the teardrop attack. For more information on the ICMP-fix, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: 154174 TITLE : Invalid ICMP Datagram Fragments Hang Windows NT, Windows 95
The modified teardrop attack works by sending pairs of deliberatelyconstructed IP fragments which are reassembled into an invalid UDPdatagram. Overlapping offsets cause the second packet to overwrite data inthe middle of the UDP header contained in the first packet in such a waythat the datagrams are left incomplete.
As Windows NT receives these invalid datagrams, it allocates kernelmemory. If enough of these invalid datagrams are received Windows NT mayhang with a STOP 0x0000000A or 0x00000019.
Windows NT 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
For your convenience, the English version of this post-SP3 hotfix has beenposted to the following Internet location. However, Microsoft recommendsthat you install Windows NT 4.0 Service Pack 4 to correct this problem.
NOTE: This fix supercedes the ICMP-fix, the OOB-fix, and the Land-fixhotfixes.
Windows NT 4.0
Microsoft has confirmed this problem could result in some degree ofsecurity vulnerability in Windows NT version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Windows NT 3.51
Microsoft has confirmed this problem could result in some degree ofsecurity vulnerability in Windows NT version 3.51. A fully supported fix isnow available, but it has not been fully regression tested and should onlybe applied to systems determined to be at risk of attack. Please evaluateyour system's physical accessibility, network and Internet connectivity,and other factors to determine the degree of risk to your system. If yoursystem is sufficiently at risk, Microsoft recommends you apply this fix.Otherwise, wait for the next Windows NT service pack, which will containthis fix. Please contact Microsoft Technical Support for more information.