misc/81202: nmap scan causes box to get immediately rebooted.

[elmer radi radisson]

>Number:         81202
>Category:       misc
>Synopsis:       nmap scan causes box to get immediately rebooted.
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 18 14:20:02 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     elmer radi radisson
>Release:        5.4 STABLE
>Organization:
klosz art company
>Environment:
FreeBSD lotos.mcnet.pl 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon May 16 16:37:31 CEST 2005     root at lotos.mcnet.pl:/usr/src/sys/i386/compile/RAVEN-X205  i386

Machine is IBM X220, P3 866Mhz+256MB RAM, Intel NIC (FXP), 3WARE ATA RAID 8000 Series
>Description:
both using machine installed out of the box (CD Install) or after upgrading kernel/system using cvsup, being exposed under nmap scan causes it to get rebooted. Besides of this, machine seems to be very stable and  all compilation/upgrade process with cvsup'ed source code went ok. Only exposure under nmap scan causes immediate reboot. So to summarize - this problem repeats with both generic kernel and compiled one (using well crafted config file). I've got CD install images from ftp2.freebsd.org and installation process went also ok. I wouldn't report it to public FreeBSD related discussion list due to the fact that I perceive this as possible trivial method to cause remote DOS (/paranoia off) especially if problem possibly has a reported wider range and this is not unique and my-box-only related.
>How-To-Repeat:
perform nmap (no matter if it is vanilla tcp scan or with any additional flags) on target freebsd 5.4 box.

      
>Fix:
   n/a
>Release-Note:
>Audit-Trail:
>Unformatted: