mailing list archives
Re: nmap ends prematurely with a segfault
From: "DePriest, Jason R." <jrdepriest () gmail com>
Date: Thu, 18 Oct 2007 15:37:17 -0500
On 10/18/07, David Fifield wrote:
On Thu, Oct 18, 2007 at 03:15:21PM -0500, DePriest, Jason R. wrote:
I run nmap like this:
sudo nmap -v -sSUV -O -pT:-,U:[1-65535] --traceroute --reason
and after some time, it eventually ends with a segfault.
Seriously, it ends with a simple "Segmentation fault" and nothing else
to help explain from where the segfault came.
I've been investigating a segfault that I found with --script=discovery.
Do these two commands segfault for you too?
nmap --script=ripeQuery.nse localhost
nmap -6 whois.ripe.net
It seems to be related to nsock and IPv6.
My nmap system is behind a proxy server and cannot successfully run
the ripeQuery script.
There aren't any IPv6 devices enabled on my network, either. I can
resolve the IPv6 address for whois.ripe.net thanks to DNS, but I
cannot get to it (because of the non-transparent proxy).
Do you know of any tests I can for you that wouldn't require my nmap
system to have Internet access?
If not, I could try tunneling nmap through a SOCKSifying tool of some sort.
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org