Some error handling on ntlm relayer
Instead of a cryptic exception, let the user know if the HTTP target isn't actually asking for WWW-Authenticate. There are likely many more opportunities to catch errors, but this is the most obvious.unstable
parent
635710402b
commit
8d187b272d
|
@ -143,7 +143,14 @@ class Metasploit3 < Msf::Auxiliary
|
||||||
case protocol
|
case protocol
|
||||||
when 'HTTP'
|
when 'HTTP'
|
||||||
resp, ser_sock = http_relay_toserver(hash)
|
resp, ser_sock = http_relay_toserver(hash)
|
||||||
|
if resp.headers["WWW-Authenticate"]
|
||||||
t2hash = resp.headers["WWW-Authenticate"].split(" ")[1]
|
t2hash = resp.headers["WWW-Authenticate"].split(" ")[1]
|
||||||
|
else
|
||||||
|
print_error "#{rhost} is not requesting authentication."
|
||||||
|
cli_sock.close
|
||||||
|
ser_sock.close
|
||||||
|
return false
|
||||||
|
end
|
||||||
when 'SMB'
|
when 'SMB'
|
||||||
t2hash, ser_sock = smb_relay_toservert1(hash)
|
t2hash, ser_sock = smb_relay_toservert1(hash)
|
||||||
end
|
end
|
||||||
|
|
Loading…
Reference in New Issue