KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q179129: STOP 0x0000000A or 0x00000019 Due to Modified Teardrop Attack

Article: Q179129
Product(s): Microsoft Windows NT
Version(s): WinNT:4.0
Operating System(s): 
Keyword(s): kbWinNT400sp4fix
Last Modified: 09-AUG-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT Workstation versions 3.51, 4.0 
- Microsoft Windows NT Server versions 3.51, 4.0 
- Microsoft Windows NT Server, Enterprise Edition version 4.0 
- Microsoft Windows NT Server version 4.0, Terminal Server Edition 
-------------------------------------------------------------------------------


SYMPTOMS
========

Windows NT may stop responding (hang) with a STOP 0x0000000A or 0x00000019
message after receiving a number of deliberately corrupted UDP packets.

CAUSE
=====

This behavior occurs due to a variation of the "teardrop" attack. Windows NT 4.0
with Service Pack 3 and the ICMP-fix is not susceptible to the original form of
the teardrop attack. For more information on the ICMP- fix, please see the
following article in the Microsoft Knowledge Base:

  ARTICLE-ID: Q154174
  TITLE : Invalid ICMP Datagram Fragments Hang Windows NT, Windows 95

The modified teardrop attack works by sending pairs of deliberately constructed
IP fragments which are reassembled into an invalid UDP datagram. Overlapping
offsets cause the second packet to overwrite data in the middle of the UDP
header contained in the first packet in such a way that the datagrams are left
incomplete.

As Windows NT receives these invalid datagrams, it allocates kernel memory. If
enough of these invalid datagrams are received Windows NT may hang with a STOP
0x0000000A or 0x00000019.


RESOLUTION
==========

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,
please see the following article in the Microsoft Knowledge Base:

  Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack


For your convenience, the English version of this post-SP3 hotfix has been posted
to the following Internet location. However, Microsoft recommends that you
install Windows NT 4.0 Service Pack 4 to correct this problem.

  ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/teardrop2-fix/

NOTE: This hotfix supersedes the fix referred to in the following articles in the
Microsoft Knowledge Base:

  ARTICLE-ID: Q143478
  TITLE : Stop 0A in Tcpip.sys When Receiving Out Of Band (OOB) Data

  ARTICLE-ID: Q154174
  TITLE : Invalid ICMP Datagram Fragments Hang Windows NT, Windows 95

  ARTICLE-ID: Q165005
  TITLE : Windows NT Slows Down Due to Land Attack

  ARTICLE-ID: Q177245
  TITLE : Multiprocessor Computer May Hang Because of Tcpip.sys

Windows NT 3.51
---------------

To resolve this problem, obtain the following fix.

This fix should have the following time stamp:

+---------------------------------------------------+
| 01/14/98 | 12:04p | 123,824 | Tcpip.sys | (Intel) | 
+---------------------------------------------------+
| 01/14/98 | 12:00p | 216,848 | Tcpip.sys | (Alpha) | 
+---------------------------------------------------+

This hotfix has been posted to the following Internet location:

  ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/hotfixes-postSP5/teardrop2-fix/

NOTE: This fix supercedes the ICMP-fix, the OOB-fix, and the Land-fix hotfixes.

STATUS
======

Windows NT 4.0
--------------

Microsoft has confirmed this problem could result in some degree of security
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 of security
vulnerability in Windows NT version 3.51. A fully supported fix is now
available, but it has not been fully regression tested and should only be
applied to systems determined to be at risk of attack. Please evaluate your
system's physical accessibility, network and Internet connectivity, and other
factors to determine the degree of risk to your system. If your system is
sufficiently at risk, Microsoft recommends you apply this fix. Otherwise, wait
for the next Windows NT service pack, which will contain this fix. Please
contact Microsoft Technical Support for more information.


Additional query words: spoof crash crashes bonk.c boink.c ntfaqipr
======================================================================
Keywords          : kbWinNT400sp4fix 
Technology        : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT351search kbWinNT400search kbWinNTW351search kbWinNTW351 kbWinNTSsearch kbWinNTSEntSearch kbWinNTSEnt400 kbWinNTS400search kbWinNTS400 kbWinNTS351 kbNTTermServ400 kbNTTermServSearch kbWinNTS351search
Version           : WinNT:4.0
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.