Re: Bug?: hang on socket_lock in p2p-conficker.nse

[Patrick Donnelly <batrick () batbytes com>]

On Feb 27, 2012 12:12 PM, "Daniel Miller" <bonsaiviking () gmail com> wrote:
> List,
>
> Not sure the best way to hunt this bug down. Here is my initial bug
report:
> > Stats: 47:39:31 elapsed; 133 hosts completed (9 up), 9 undergoing Script
Scan
> > NSE: Active NSE Script Threads: 1 (1 waiting)
> >
> > NSE Timing: About 99.88% done; ETC: 16:59 (0:03:28 remaining)
> > NSE: Waiting: 'p2p-conficker' (thread: 0xb2aee28)
> >        stack traceback:
> >                [C]: in function 'connect'
> >                [string "local connect, socket_lock = ...;..."]:4: in
function 'connect'
> >
 ...sr/local/bin/../share/nmap/scripts/p2p-conficker.nse:471: in function
'conficker_check'
> >
 ...sr/local/bin/../share/nmap/scripts/p2p-conficker.nse:602: in function
<...sr/local/bin/../share/nmap/scripts/p2p-conficker.nse:533>
> >                (tail call): ?
>
> Command line: sudo nmap -v -A -oA full-%y%m%d --script 'all and not dos
and not qscan and not fuzzer and not external' --reason --log-errors
192.168.1.0/24
> I have run this twice with same result: execution hangs for hours/days on
this line in p2p-conficker. Any guidance as to how to debug this would be
great.

I can tell you that the hang is in the actual connect function not
socket_lock. The first stack frame would say socket_lock instead of connect
otherwise. I suspect the problem is the connection attempt is not timing
out? I can't look at the code right now from my phone.

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