From nobody@FreeBSD.org  Wed May 18 14:12:07 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7966616A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 May 2005 14:12:07 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5348543D62
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 May 2005 14:12:07 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j4IEC27h044508
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 May 2005 14:12:02 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j4IEC2kn044507;
	Wed, 18 May 2005 14:12:02 GMT
	(envelope-from nobody)
Message-Id: <200505181412.j4IEC2kn044507@www.freebsd.org>
Date: Wed, 18 May 2005 14:12:02 GMT
From: elmer radi radisson <fbsd@aesthetic.eu.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: nmap scan causes box to get immediately rebooted. 
X-Send-Pr-Version: www-2.3

>Number:         81202
>Category:       kern
>Synopsis:       nmap scan causes box to get immediately rebooted.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    glebius
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 18 14:20:02 GMT 2005
>Closed-Date:    Mon Jan 29 11:35:53 GMT 2007
>Last-Modified:  Mon Jan 29 11:35:53 GMT 2007
>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@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:

From: elmer radi radisson <fbsd@aesthetic.eu.org>
To: bug-followup@FreeBSD.org, fbsd@aesthetic.eu.org
Cc:  
Subject: Re: misc/81202: nmap scan causes box to get immediately rebooted.
Date: Wed, 18 May 2005 19:06:11 +0200

 correction: this message was intended to be sent at security contact but 
 I was advised to rather ask about this problem using  other contact 
 place - so did anyone noticed similar behaviour? I've got some feedback
 from colleagues using the nearly the same box setup and nobody was able
 to reproduce such situation.
 Moreower, there is no other evidence of this problem in syslog messages,
 machine is just rebooting immediately and silently.
 
 
 -- 
 No virus found in this outgoing message.
 Checked by AVG Anti-Virus.
 Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 2005-05-13
 
Responsible-Changed-From-To: freebsd-bugs->glebius 
Responsible-Changed-By: glebius 
Responsible-Changed-When: Mon May 23 13:53:40 GMT 2005 
Responsible-Changed-Why:  
I'll try to work on this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=81202 

From: Gleb Smirnoff <glebius@FreeBSD.org>
To: elmer radi radisson <fbsd@aesthetic.eu.org>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/81202: nmap scan causes box to get immediately rebooted.
Date: Mon, 23 May 2005 17:56:51 +0400

   Elmer,
 
 On Wed, May 18, 2005 at 02:12:02PM +0000, elmer radi radisson wrote:
 e> >Synopsis:       nmap scan causes box to get immediately rebooted.
 
 1) Can you please show your rc.conf?
 2) Do you run X when box is rebooted? If you do, can you please
    switch to text console before running nmap and see whether panic
    messages are printed?
 
 -- 
 Totus tuus, Glebius.
 GLEBIUS-RIPN GLEB-RIPE

From: elmer radi radisson <fbsd@aesthetic.eu.org>
To: Gleb Smirnoff <glebius@FreeBSD.org>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re[2]: misc/81202: nmap scan causes box to get immediately rebooted.
Date: Mon, 23 May 2005 17:06:51 +0200

 > 1) Can you please show your rc.conf?
 
 right now I can't  - this machine is turned off and out of my range.
 but while I was on the same track it rather turned out to be false
 suspicion. I tried some limitations even with almost empty file
 /containing only basic network settings but effect still remains the same.
 
 > 2) Do you run X when box is rebooted? If you do, can you please
 >    switch to text console before running nmap and see whether panic
 >    messages are printed?
 
 no, I don't. Moreover, I tried to test it also with no daemons
 enabled on network interface, but to no avail.
 
 Unfortunately I can't see any panic messages printed on the screen
 under all circumstances. Machine just reboots silently so that somehow
 problem seems to be hardware related but this machine just perform
 perfectly while running with other processing/network tasks as
 well as successfully compiling/building  kernel/world. Only nmap
 scan forces it to kneel down. I will try to move with my entire RAID
 configuration to other identical machine and compare results.
 
 
 
 
 --
 
 *** Machines are humans. We`re programmed that way ***
 
State-Changed-From-To: open->feedback 
State-Changed-By: glebius 
State-Changed-When: Fri Oct 13 13:24:04 UTC 2006 
State-Changed-Why:  
Any update on this problem? Is the problem still present 
on latest FreeBSD releases? Have you tried to change the 
hardware, as planned? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=81202 
State-Changed-From-To: feedback->closed 
State-Changed-By: glebius 
State-Changed-When: Mon Jan 29 11:34:52 UTC 2007 
State-Changed-Why:  
Feedback timeout. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=81202 
>Unformatted:
