Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




nmap-dev logo Nmap Development mailing list archives

nmap crash
From: "Ganga Bhavani" <GBhavani () everdreamcorp com>
Date: Wed, 5 Apr 2006 00:42:52 -0700

Hi,

nmap 3.95 crashed on a korean windows system when executed with  the following params

nmap -O -F -oN out.nmap --host_timeout=900000 10.10.188.0/20.

The dump shows the following trace.  

nmap!_output+0x4f2 [f:\vs70builds\9466\vc\crtbld\crt\src\output.c @ 707]
nmap!_snprintf+0x2e [f:\vs70builds\9466\vc\crtbld\crt\src\sprintf.c @ 104]
nmap!Target::NameIP+0x25
nmap!Target::NameIP+0x24
nmap!nexthost+0x3bf
nmap!nmap_main+0x25e6
nmap!main+0x331
nmap!mainCRTStartup+0x170 [f:\vs70builds\9466\vc\crtbld\crt\src\crt0.c @ 259]

On further investigation, I traced the crash in the fatal function in nexthost() in targets.cc.

 fatal("%s: Failed to determine dst MAC address for target %s", 
               __FUNCTION__, hs->hostbatch[hidx]->NameIP());

 Is there a reason why hidx is used?  Shouldnt it be 'i' instead of hidx?

-Ganga



_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev


  By Date           By Thread  

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