Nmap Development mailing list archives
Version scanning problem with "--version-intensity 0"
From: Makoto Shiotsuki <shio () st rim or jp>
Date: Mon, 05 Jun 2006 14:16:51 +0900
Version scanning against udp ports with "--version-intensity 0" option causes nmap to crash. The following is an example scanning result against normal W2K box. ------------------------------------------------------- # nmap -n -sU -sV 192.168.183.12 --version-intensity 0 Starting Nmap 4.04BETA1 ( http://www.insecure.org/nmap/ ) at 2006-06-05 01:23 JST nmap: service_scan.cc:1690: int send_probe_text (void *, void *, ServiceNFO *, ServiceProbe *): Assertion `probe' failed. Aborted (core dumped) ------------------------------------------------------- I think this seems to happen when the target port is not specified by "ports" directive in the nmap-service-probes file at all. (ie. no probes will be executed against that port) In this case, "send_probe_text(nsp, nsi, svc, probe)" is called in the function "servicescan_connect_handler()" with "probe" value NULL, so that, "assert(probe)" fails at line 1690 in service_scan.cc. Makoto Shiotsuki _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev
Current thread:
- Version scanning problem with "--version-intensity 0" Makoto Shiotsuki (Jun 04)
- Re: Version scanning problem with "--version-intensity 0" doug (Jun 05)
- Re: Version scanning problem with "--version-intensity 0" Makoto Shiotsuki (Jun 05)
- Re: Version scanning problem with "--version-intensity 0" Fyodor (Jun 08)
- Re: Version scanning problem with "--version-intensity 0" doug (Jun 05)