Home page logo
/

nmap-dev logo Nmap Development mailing list archives

[BUG] Nmap host specification parsing
From: ithilgore <ithilgore.ryu.l () gmail com>
Date: Sun, 14 Jun 2009 03:43:12 +0300

It applies to the latest svn version and the problem is that when
you put an extra comma ',' after any host, then Nmap adds an
additional target to the list. The target is the IP that corresponds
to 0 for the least significant byte and for the rest of the bytes to
the same class network as the host before the comma.

$ nmap -sL -n 10.0.0.1, 10.0.0.2

Starting Nmap 4.85BETA10 ( http://nmap.org ) at 2009-06-14 03:33 EEST

Host 10.0.0.1 not scanned
Host 10.0.0.0 not scanned
Host 10.0.0.2 not scanned
Nmap done: 3 IP addresses (0 hosts up) scanned in 0.00 seconds


$ nmap -sL -n 10.0.0.1, 192.168.0.10,

Starting Nmap 4.85BETA10 ( http://nmap.org ) at 2009-06-14 03:38 EEST

Host 10.0.0.1 not scanned
Host 10.0.0.0 not scanned
Host 192.168.0.10 not scanned
Host 192.168.0.0 not scanned
Nmap done: 4 IP addresses (0 hosts up) scanned in 0.00 seconds


Something is obviously wrong with the parsing. I didn't have time to
check where the problem in the code is but I would start by looking
at TargetGroup::parse_expr() at TargetGroup.cc

-- ithilgore





_______________________________________________
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 ]
AlienVault