Hang on SNMP script?

[Christopher Clements <christopher.a.clements () gmail com>]

More info on the specific script running:

NSE Timing: About 99.99% done; ETC: 16:38 (0:00:04 remaining)
NSE: Running: 'snmp-win32-software' (thread: 0x69e6d20)
        stack traceback:
                [C]: in function 'send'
                /usr/local/bin/../share/nmap/nselib/snmp.lua:479: in
function 'snmpWalk'

.../local/bin/../share/nmap/scripts/snmp-win32-software.nse:96: in function
<.../local/bin/../share/nmap/scripts/snmp-win32-software.nse:84>
                (...tail calls...)


---------- Forwarded message ----------
From: Christopher Clements <christopher.a.clements () gmail com>
Date: Thu, Sep 13, 2012 at 4:36 PM
Subject: Hang on SNMP script?
To: nmap-dev () insecure org


I've been running an internal scan for the past 24 hours with the following
options:

nmap -A -vvv -sSUCV --reason --open <targets>


however, it seems to be hung at this point for the past 12:

NSE Timing: About 99.99% done; ETC: 16:31 (0:00:03 remaining)
Stats: 22:15:16 elapsed; 52 hosts completed (128 up), 128 undergoing Script
Scan
NSE: Active NSE Script Threads: 1 (0 waiting)


If I increase to debug level 3, I have seen these messages happening for
the past 12 hours:


NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | SEND
NSE: UDP 10.1.136.66:45037 < 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a2 1e 02 0+     public
00000010: 02 6f 0c 02 01 05 02 01 01 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a1 1e 02 0+     public
00000010: 02 6f 0c 02 01 00 02 01 00 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | SEND
NSE: UDP 10.1.136.66:45037 < 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a2 1e 02 0+     public
00000010: 02 6f 0c 02 01 05 02 01 01 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a1 1e 02 0+     public
00000010: 02 6f 0c 02 01 00 02 01 00 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | SEND
NSE: UDP 10.1.136.66:45037 < 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a2 1e 02 0+     public
00000010: 02 6f 0c 02 01 05 02 01 01 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a1 1e 02 0+     public
00000010: 02 6f 0c 02 01 00 02 01 00 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | SEND
NSE: UDP 10.1.136.66:45037 < 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a2 1e 02 0+     public
00000010: 02 6f 0c 02 01 05 02 01 01 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00                    h

NSE: UDP 10.1.136.66:45037 > 192.168.0.4:161 | 00000000: 30 2b 02 01 00 04
06 70 75 62 6c 69 63 a1 1e 02 0+     public
00000010: 02 6f 0c 02 01 00 02 01 00 30 12 30 10 06 0c 2b  o       0 0   +
00000020: 06 01 02 01 19 06 03 01 05 81 68 05 00


Any ideas about what might be happening here?
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/