Nmap ms-sql-dump-hashes NSE Script


This page contains detailed information about how to use the ms-sql-dump-hashes NSE script. For list of all NSE scripts, visit the Nmap NSE Library.

Select:
Overview
Error Messages

Script Overview

Script source code: https://github.com/nmap/nmap/tree/master/scripts/ms-sql-dump-hashes.nse
Script categories: auth, discovery, safe
Target service / protocol: ms-sql-s
Target network port(s): 1433
List of CVEs: -

Script Description

The ms-sql-dump-hashes.nse script dumps the password hashes from an MS-SQL server in a format suitable for cracking by tools such as John-the-ripper. In order to do so the user needs to have the appropriate DB privileges.

Credentials passed as script arguments take precedence over credentials discovered by other scripts.

Ms-sql-dump-hashes NSE Script Arguments

This is a full list of arguments supported by the ms-sql-dump-hashes.nse script:

ms-sql-dump-hashes.dir

Dump hashes to a file in this directory. File name is <ip>_<instance>_ms-sql_hashes.txt. Default: no file is saved.

smbdomain

The domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.

smbhash

A password hash to use when logging in. This is given as a single hex string (32 characters) or a pair of hex strings (both 32 characters, optionally separated by a single character). These hashes are the LanMan or NTLM hash of the user's password, and are stored on disk or in memory. They can be retrieved from memory using the fgdump or pwdump tools.

smbnoguest

Use to disable usage of the 'guest' account.

smbpassword

The password to connect with. Be cautious with this, since some servers will lock accounts if the incorrect password is given. Although it's rare that the Administrator account can be locked out, in the off chance that it can, you could get yourself in trouble. To use a blank password, leave this parameter off altogether.

smbtype

The type of SMB authentication to use. These are the possible options:

  • v1: Sends LMv1 and NTLMv1.
  • LMv1: Sends LMv1 only.
  • NTLMv1: Sends NTLMv1 only (default).
  • v2: Sends LMv2 and NTLMv2.
  • LMv2: Sends LMv2 only.
  • NTLMv2: Doesn't exist; the protocol doesn't support NTLMv2 alone. The default, NTLMv1, is a pretty decent compromise between security and compatibility. If you are paranoid, you might want to use v2 or lmv2 for this. (Actually, if you're paranoid, you should be avoiding this protocol altogether!). If you're using an extremely old system, you might need to set this to v1 or lm, which are less secure but more compatible. For information, see smbauth.lua.

smbusername

The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN" are not understood. To set a domain, use the smbdomain argument.

randomseed

Set to a value to change the filenames/service names that are randomly generated.

smbbasic

Forces the authentication to use basic security, as opposed to "extended security". Against most modern systems, extended security should work, but there may be cases where you want to force basic. There's a chance that you'll get better results for enumerating users if you turn on basic authentication.

smbport

Override the default port choice. If smbport is open, it's used. It's assumed to be the same protocol as port 445, not port 139. Since it probably isn't possible to change Windows' ports normally, this is mostly useful if you're bouncing through a relay or something.

smbsign

Controls whether or not server signatures are checked in SMB packets. By default, on Windows, server signatures aren't enabled or required. By default, this library will always sign packets if it knows how, and will check signatures if the server says to. Possible values are:

  • force: Always check server signatures, even if server says it doesn't support them (will Probably fail, but is technically more secure).
  • negotiate: [default] Use signatures if server supports them.
  • ignore: Never check server signatures. Not recommended.
  • disable: Don't send signatures, at all, and don't check the server's. not recommended. More information on signatures can be found in smbauth.lua.

mssql.domain

The domain against which to perform integrated authentication. When set, the scripts assume integrated authentication should be performed, rather than the default sql login.

mssql.instance-all

Targets all SQL server instances discovered through the browser service.

mssql.instance-name

The name of the instance to connect to.

mssql.instance-port

The port of the instance to connect to.

mssql.password

The password for mssql.username. If this argument is not given but mssql.username, a blank password is used.

mssql.protocol

The protocol to use to connect to the instance. The protocol may be either NP,Named Pipes or TCP.

mssql.scanned-ports-only

If set, the script will only connect to ports that were included in the Nmap scan. This may result in instances not being discovered, particularly if UDP port 1434 is not included. Additionally, instances that are found to be running on ports that were not scanned (e.g. if 1434/udp is in the scan and the SQL Server Browser service on that port reports an instance listening on 43210/tcp, which was not scanned) will be reported but will not be stored for use by other ms-sql-* scripts.

mssql.timeout

How long to wait for SQL responses. This is a number followed by ms for milliseconds, s for seconds, m for minutes, or h for hours. Default: 30s.

mssql.username

The username to use to connect to SQL Server instances. This username is used by scripts taking actions that require authentication (e.g. ms-sql-query) This username (and its associated password) takes precedence over any credentials discovered by the ms-sql-brute and ms-sql-empty-password scripts.

- - -
To use these script arguments, add them to the Nmap command line using the --script-args arg1=value,[arg2=value,..] syntax. For example:

nmap --script=ms-sql-dump-hashes --script-args ms-sql-dump-hashes.dir=value,smbdomain=value <target>

Ms-sql-dump-hashes NSE Script Example Usage

Here's an example of how to use the ms-sql-dump-hashes.nse script:

nmap -p 1433 <ip> --script ms-sql-dump-hashes

Ms-sql-dump-hashes NSE Script Example Output

Here's a sample output from the ms-sql-dump-hashes.nse script:

PORT     STATE SERVICE
1433/tcp open  ms-sql-s
| ms-sql-dump-hashes:
|   nmap_test:0x01001234567890ABCDEF01234567890ABCDEF01234567890ABCDEF01234567890ABCDEF01234567890ABCDEF0123
|   sa:0x01001234567890ABCDEF01234567890ABCDEF01234567890ABCDEF01234567890ABCDEF01234567890ABCDEF0123
|_  webshop_dbo:0x01001234567890ABCDEF01234567890ABCDEF01234567890ABCDEF01234567890ABCDEF01234567890ABCDEF0123

Ms-sql-dump-hashes NSE Script Example XML Output

There is no sample XML output for this module. However, by providing the -oX <file> option, Nmap will produce a XML output and save it in the file.xml file.

Author

  • Patrik Karlsson

References

See Also

Related NSE scripts to the ms-sql-dump-hashes.nse script:

Visit Nmap NSE Library for more scripts.

The ms-sql-dump-hashes.nse script may fail with the following error messages. Check for the possible causes by using the code snippets highlighted below found in the script source code. This can often times help in identifying the root cause of the problem.

Failed to open file (%s)

Here is a relevant code snippet related to the "Failed to open file (%s)" error message:

97:	-- @return status true on success, false on failure
98:	-- @return err string containing the error if status is false
99:	local function saveToFile(filename, response)
100:	  local f = io.open( filename, "w")
101:	  if ( not(f) ) then
102:	    return false, ("Failed to open file (%s)"):format(filename)
103:	  end
104:	  for _, row in ipairs(response) do
105:	    if ( not(f:write(row .."\n" ) ) ) then
106:	      return false, ("Failed to write file (%s)"):format(filename)
107:	    end

Failed to write file (%s)

Here is a relevant code snippet related to the "Failed to write file (%s)" error message:

101:	  if ( not(f) ) then
102:	    return false, ("Failed to open file (%s)"):format(filename)
103:	  end
104:	  for _, row in ipairs(response) do
105:	    if ( not(f:write(row .."\n" ) ) ) then
106:	      return false, ("Failed to write file (%s)"):format(filename)
107:	    end
108:	  end
109:	  f:close()
110:	  return true
111:	end

Version

This page has been created based on Nmap version 7.92.

Go back to menu.