Editing WinNuke (section)

==Details==
The so-called OOB simply means that the malicious TCP packet contained an [[TCP header|Urgent pointer]] (URG). The "Urgent pointer" is a rarely used field in the TCP header, used to indicate that some of the data in the TCP stream should be processed quickly by the recipient. Affected operating systems did not handle the Urgent pointer field correctly.

A person under the screen-name "_eci" published [[C (programming language)|C]] [[source code]] for the exploit on May 9, 1997.<ref>{{cite web|url=http://insecure.org/sploits/windows.OOB.DOS.html |title=Windows NT/95/3.11 Out Of Band (OOB) data barf |publisher=Insecure.org |date= |accessdate=2010-09-23}}</ref> With the source code being widely used and distributed, Microsoft was forced to create security patches, which were released a few weeks later.  For a time, numerous flavors of this exploit appeared going by such names as fedup, gimp, killme, killwin, knewkem, liquidnuke, mnuke, netnuke, muerte, nuke, nukeattack, nuker102, pnewq, project1, {{Not a typo|pstlince}}, simportnuke, sprite, sprite32, vconnect, vzmnuker, wingenocide, winnukeit, winnuker02, winnukev95, wnuke3269, wnuke4, and wnuke95.

A company called SemiSoft Solutions from New Zealand created a small program, called AntiNuke, that blocks WinNuke without having to install the official patch.<ref>[http://robert.grefstad.com/win/error_winnuke.html Windows OOB Bug, also known as WinNuke] {{Webarchive|url=https://web.archive.org/web/20110526041251/http://robert.grefstad.com/win/error_winnuke.html |date=2011-05-26 }}. Grefstad.com.</ref>