[Bug 503432] [NEW] nmap scans wrong network when invalid (?) range specified

[Mike Coleman]

Public bug reported:

Binary package hint: nmap

Description:	Ubuntu 9.10
Release:	9.10

nmap:
  Installed: 5.00-2
  Candidate: 5.00-2
  Version table:
 *** 5.00-2 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status


$ sudo nmap -sP 192.168.220/24
Starting Nmap 5.00 ( http://nmap.org ) at 2010-01-05 09:44 CST
Host 192.168.0.0 is up (0.0030s latency).
Host 192.168.0.1 is up (0.00069s latency).
Host 192.168.0.2 is up (0.00081s latency).
Host 192.168.0.3 is up (0.00095s latency).
Host 192.168.0.4 is up (0.0026s latency).
...

This is the wrong network.  If nmap doesn't like this syntax, it should
abort with an error.  Otherwise it should be scanning 192.168.220.*, not
192.168.0.*.

** Affects: nmap (Ubuntu)
     Importance: Undecided
         Status: New

-- 
nmap scans wrong network when invalid (?) range specified
https://bugs.launchpad.net/bugs/503432
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nmap in ubuntu.