Nmap ms-sql-tables NSE Script


This page contains detailed information about how to use the ms-sql-tables 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-tables.nse
Script categories: discovery, safe
Target service / protocol: ms-sql-s
Target network port(s): 1433
List of CVEs: -

Script Description

The ms-sql-tables.nse script queries Microsoft SQL Server (ms-sql) for a list of tables per database.

SQL Server credentials required: Yes (use ms-sql-brute, ms-sql-empty-password and/or mssql.username & mssql.password) Run criteria:

  • Host script: Will run if the mssql.instance-all, mssql.instance-name or mssql.instance-port script arguments are used (see mssql.lua).
  • Port script: Will run against any services identified as SQL Servers, but only if the mssql.instance-all, mssql.instance-name and mssql.instance-port script arguments are NOT used.

The sysdatabase table should be accessible by more or less everyone.

Once we have a list of databases we iterate over it and attempt to extract table names. In order for this to succeed we need to have either sysadmin privileges or an account with access to the db. So, each database we successfully enumerate tables from we mark as finished, then iterate over known user accounts until either we have exhausted the users or found all tables in all the databases.

System databases are excluded.

NOTE: Communication with instances via named pipes depends on the smb library. To communicate with (and possibly to discover) instances via named pipes, the host must have at least one SMB port (e.g. TCP 445) that was scanned and found to be open. Additionally, named pipe connections may require Windows authentication to connect to the Windows host (via SMB) in addition to the authentication required to connect to the SQL Server instances itself. See the documentation and arguments for the smb library for more information.

NOTE: By default, the ms-sql-* scripts may attempt to connect to and communicate with ports that were not included in the port list for the Nmap scan. This can be disabled using the mssql.scanned-ports-only script argument.

Ms-sql-tables NSE Script Arguments

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

ms-sql-tables.keywords

If set shows only tables or columns matching the keywords

ms-sql-tables.maxdb

Limits the amount of databases that are processed and returned (default 5). If set to zero or less all databases are processed.

ms-sql-tables.maxtables

Limits the amount of tables returned (default 5). If set to zero or less all tables are returned.

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-tables --script-args ms-sql-tables.keywords=value,ms-sql-tables.maxdb=value <target>

Ms-sql-tables NSE Script Example Usage

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

nmap -p 1433 --script ms-sql-tables --script-args mssql.username=sa,mssql.password=sa <host>

Ms-sql-tables NSE Script Example Output

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

| ms-sql-tables:
|   [192.168.100.25\MSSQLSERVER]
|   webshop
|     table	column	type	length
|     payments	user_id	int	4
|     payments	purchase_id	int	4
|     payments	cardholder	varchar	50
|     payments	cardtype	varchar	50
|     payments	cardno	varchar	50
|     payments	expiry	varchar	50
|     payments	cvv	varchar	4
|     products	id	int	4
|     products	manu	varchar	50
|     products	model	varchar	50
|     products	productname	varchar	100
|     products	price	float	8
|     products	imagefile	varchar	255
|     products	quantity	int	4
|     products	keywords	varchar	100
|     products	description	text	16
|     users	id	int	4
|     users	username	varchar	50
|     users	password	varchar	50
|_    users	fullname	varchar	100

Ms-sql-tables 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-tables.nse script:

Visit Nmap NSE Library for more scripts.

The ms-sql-tables.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.

ERROR: No login credentials.

Here is a relevant code snippet related to the "ERROR: No login credentials." error message:

151:	  db_query = ("SELECT %s name from master..sysdatabases WHERE name NOT IN (%s)"):format(db_limit, table.concat(exclude_dbs, ","))
152:	
153:	
154:	  local creds = mssql.Helper.GetLoginCredentials_All( instance )
155:	  if ( not creds ) then
156:	    output = "ERROR: No login credentials."
157:	  else
158:	    for username, password in pairs( creds ) do
159:	      local helper = mssql.Helper:new()
160:	      status, result = helper:ConnectEx( instance )
161:	      if ( not(status) ) then

Version

This page has been created based on Nmap version 7.92.

Go back to menu.