From 3c87635ae82de27440b6aedcc24f826d1ad47dce Mon Sep 17 00:00:00 2001 From: david Date: Thu, 18 Oct 2012 03:47:22 +0000 Subject: [PATCH] Use nmap.new_socket in place of nmap:new_socket in smb-check-vulns.nse. Kit Peters reported the crash: smb-check-vulns.nse:366: calling 'new_socket' on bad self (string expected, got table) http://seclists.org/nmap-dev/2012/q4/124 --- scripts/smb-check-vulns.nse | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/smb-check-vulns.nse b/scripts/smb-check-vulns.nse index 8cd366e4e..151d14ca7 100644 --- a/scripts/smb-check-vulns.nse +++ b/scripts/smb-check-vulns.nse @@ -373,7 +373,7 @@ local function check_smbv2_dos(host) string.char(0x4d, 0x20, 0x30, 0x2e, 0x31, 0x32, 0x00, 0x02, 0x53, 0x4d, 0x42, 0x20, 0x32, 0x2e) .. string.char(0x30, 0x30, 0x32, 0x00) - local socket = nmap:new_socket() + local socket = nmap.new_socket() if(socket == nil) then return false, "Couldn't create socket" end @@ -398,7 +398,7 @@ local function check_smbv2_dos(host) stdnse.sleep(5) -- Create a new socket - socket = nmap:new_socket() + socket = nmap.new_socket() if(socket == nil) then return false, "Couldn't create socket" end