Home page logo

nmap-dev logo Nmap Development mailing list archives

nmap ends prematurely with a segfault
From: "DePriest, Jason R." <jrdepriest () gmail com>
Date: Thu, 18 Oct 2007 15:15:21 -0500

I run nmap like this:
sudo nmap -v -sSUV -O -pT:-,U:[1-65535] --traceroute --reason
--script=discovery,safe,backdoor,vulnerability,malware --script-trace
-d6 xxx.yyy.zzz.190,153,193,89

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.

The last bit looks like this:
NSOCK (1524.9210s) Callback: READ SUCCESS for EID 770
[xxx.yyy.zzz.153:5988] (69 bytes): HTTP/1.1 401
Unauthorized..WWW-Authenticate: Basic realm="ANLYX2"....
SCRIPT ENGINE: TCP xxx.yyy.zzz.50:34039 < xxx.yyy.zzz.153:5988 |
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Basic realm="ANLYX2"

NSOCK (1524.9210s) msevent_delete (IOD #28) (EID #770)
NSOCK (1524.9210s) wait_for_events
NSOCK (1524.9210s) PCAP read_on_nonselect
NSOCK (1524.9210s) PCAP END read_on_nonselect
SCRIPT ENGINE: TCP xxx.yyy.zzz.50:34039 > xxx.yyy.zzz.153:5988 | CLOSE
Segmentation fault

I am attaching a file with all the output starting from when SCRIPT
ENGINE first showed up.  I hope anyway.  I could only scroll back 5000
lines.  If you need more, I can run it again (it is reproducible) and
tee the output or something.


Attachment: nmap-segfault-01.7z

Sent through the nmap-dev mailing list
Archived at http://SecLists.Org

  By Date           By Thread  

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