Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: nmap (win32 4.60) bug and a fix
From: Ionreflex <ionreflex () gmail com>
Date: Wed, 9 Apr 2008 11:18:57 -0400

Hi all,

I tried to reproduce the problem to no avail on an up-to-date WindeXP!
Without any option, this is what I get :

[snap]
C:\Program Files\Nmap>nmap 192.168.51.255

Starting Nmap 4.60 ( http://insecure.org ) at 2008-04-09 11:11 Est (heure
d'ÚtÚ)

Note: Host seems down. If it is really up, but blocking our ping probes, try
-PN

Nmap done: 1 IP address (0 hosts up) scanned in 0.610 seconds
[/snap]

Problem is the IP address - 192.168.51.255 - could be a valid unicast, it
all depends on the subnet mask...

Dudi, could you be more specific about the Win32 version and maybe the
command you try to pass ? I just want to make sure the problem is specific
to Nmap and not the host itself...

Tankiou,



Ion

2008/4/8, Fyodor <fyodor () insecure org>:

On Mon, Mar 31, 2008 at 03:21:32PM +0300, Dudi I wrote:
Hi,

I found a problem with nmap (4.60) when running on win32.
when i scan an ip address which is a broadcast address (like
192.169.1.255)
nmap gets into an infinite loop.

its seems that the return code from getsockopt in this case is not
handled
at all (a 'Strange read error ...' message is produced) and nmap gets
into
an infinite loop.

Attached is the diff file to fix this issue.

Thanks Dudi.  I've applied this for the next Nmap release.

-F

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]