mailing list archives
Potential bug in nmap or ftp-anon script
From: "Sina Bahram" <sbahram () nc rr com>
Date: Thu, 4 Jun 2009 23:44:43 -0400
When I scan a specific IP address running an ftp server which allows
anonymous logins, with the anonymous ftp script, I receive the appropriate
However, if I scan a series of IP addresses, one of which includes this IP,
that particular IP doesn't have the appropriate output from the anonymous
ftp script. It does show that IP having port 21 open, but doesn't fire off
the appropriate anonymous message.
Example with fake addresses:
nmap --script ftp-anon -p21 18.104.22.168
Shows the right stuff
nmap --script ftp-anon -p21 1.2.3-5.*
Just shows 22.214.171.124 as having ftp 21 open, but no luck on the anonymous
script firing off the right message.
It does show other hosts like 126.96.36.199 or 188.8.131.52 having 21 open and
displays the anonymous message for them, so this is how I know the script is
The strange thing, of course, is that other Ips in that range trigger the
appropriate response from the script, and they all seem to be correct.
However, I'm now positive that it is missing some.
Using nmap 4.85 beta 9
I was about to gather some data for a little report, and now I suddenly have
no confidence in the accuracy of this data anymore.
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org
- Potential bug in nmap or ftp-anon script Sina Bahram (Jun 05)