Unexpected error in NSE_TYPE_READ callback. Error code: 10052 (Unknown error) QUITTING!

[Ryan Russell <ryan () thievco com>]

Nmap 6.00 and 5.21-r17497:

Starting Nmap 5.21-r17497 ( http://nmap.org ) at 2012-06-28 15:10
Pacific Daylight Time

Unexpected error in NSE_TYPE_READ callback.  Error code: 10052 (Unknown
error) QUITTING!

Starting Nmap 6.00 ( http://nmap.org ) at 2012-06-28 15:40 Pacific
Daylight Time

Unexpected error in NSE_TYPE_READ callback.  Error code: 10052 (Unknown
error) QUITTING!

I did do some searching, and saw some similar reports in much earlier
versions of nmap. But they were also in the context of having been fixed.

I narrowed down the smallest test case I could:

"\Program Files (x86)\Nmap\nmap.exe" -sV -sU -p U:999 10.24.4.1

The -sV parameter is the key one. It will still happen if you leave off
the single UDP port to check, but just takes longer. The port number is
arbitrary. It might need to be one that is NOT listening, not sure.

I've attached a pcap of the packets sent during the process. But it
basically shows it sending a couple empty UDP packets, followed by a UDP
packet that Wireshark decodes as a Portmap request. Seems like nmap
bails with the above error messages right after sending the portmap packet.

This is on Windows 7 Enterprise 64-bit, WinPcap 4.1.2.

                                        Ryan

Attachment: error.pcap
Description:

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