Nmap imap-ntlm-info NSE Script


This page contains detailed information about how to use the imap-ntlm-info 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/imap-ntlm-info.nse
Script categories: default, discovery, safe
Target service / protocol: imap, imaps
Target network port(s): 143, 993
List of CVEs: -

Script Description


The imap-ntlm-info.nse script enumerates information from remote IMAP services with NTLM authentication enabled.

Sending an IMAP NTLM authentication request with null credentials will cause the remote service to respond with a NTLMSSP message disclosing information to include NetBIOS, DNS, and OS build version.

Imap-ntlm-info NSE Script Arguments


This is a full list of arguments supported by the imap-ntlm-info.nse script:

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.

smtp.domain

The domain to be returned by get_domain, overriding the target's own domain name.

tls.servername

Hostname to use in the Server Name Indication (SNI) extension. Overrides the target name given on the command line and affects all targets.

- - -
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=imap-ntlm-info --script-args smbdomain=value,smbhash=value <target>

Imap-ntlm-info NSE Script Example Usage


Here's an example of how to use the imap-ntlm-info.nse script:

nmap -p 143,993 --script imap-ntlm-info <target>

Imap-ntlm-info NSE Script Example Output


Here's a sample output from the imap-ntlm-info.nse script:

143/tcp   open     imap
| imap-ntlm-info:
|   Target_Name: ACTIVEIMAP
|   NetBIOS_Domain_Name: ACTIVEIMAP
|   NetBIOS_Computer_Name: IMAP-TEST2
|   DNS_Domain_Name: somedomain.com
|   DNS_Computer_Name: imap-test2.somedomain.com
|   DNS_Tree_Name: somedomain.com
|_  Product_Version: 6.1.7601

Imap-ntlm-info NSE Script Example XML Output


Here's a sample XML output from the imap-ntlm-info.nse script produced by providing the -oX <file> Nmap option:

 <elem key="Target_Name">ACTIVEIMAP</elem>
 <elem key="NetBIOS_Domain_Name">ACTIVEIMAP</elem>
 <elem key="NetBIOS_Computer_Name">IMAP-TEST2</elem>
 <elem key="DNS_Domain_Name">somedomain.com</elem>
 <elem key="DNS_Computer_Name">imap-test2.somedomain.com</elem>
 <elem key="DNS_Tree_Name">somedomain.com</elem>
 <elem key="Product_Version">6.1.7601</elem>

Author


  • Justin Cacak

References


See Also


Related NSE scripts to the imap-ntlm-info.nse script:

Visit Nmap NSE Library for more scripts.

The imap-ntlm-info.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.

starttls error: %s


Here is a relevant code snippet related to the "starttls error: %s" error message:

73:	  if starttls then
74:	    local status
75:	    status, socket = starttls(host, port)
76:	    if not status then
77:	      -- could be socket problems, but more likely STARTTLS not supported.
78:	      stdnse.debug1("starttls error: %s", socket)
79:	      socket = nil
80:	    end
81:	  end
82:	  if not socket then
83:	    local line, bopt, first_line

connection error: %s


Here is a relevant code snippet related to the "connection error: %s" error message:

81:	  end
82:	  if not socket then
83:	    local line, bopt, first_line
84:	    socket, line, bopt, first_line = comm.tryssl(host, port, "" , {recv_before=true})
85:	    if not socket then
86:	      stdnse.debug1("connection error: %s", line)
87:	      return nil
88:	    end
89:	  end
90:	
91:	  socket:send("000b AUTHENTICATE NTLM\r\n")

Socket receive failed: %s


Here is a relevant code snippet related to the "Socket receive failed: %s" error message:

89:	  end
90:	
91:	  socket:send("000b AUTHENTICATE NTLM\r\n")
92:	  local status, response = socket:receive()
93:	  if not status then
94:	    stdnse.debug1("Socket receive failed: %s", response)
95:	    return nil
96:	  end
97:	  if not response then
98:	    stdnse.debug1("No response to AUTHENTICATE NTLM")
99:	    return nil

Socket receive failed: %s


Here is a relevant code snippet related to the "Socket receive failed: %s" error message:

100:	  end
101:	
102:	  socket:send(ntlm_auth_blob .. "\r\n")
103:	  status, response = socket:receive()
104:	  if not status then
105:	    stdnse.debug1("Socket receive failed: %s", response)
106:	    return nil
107:	  end
108:	  if not response then
109:	    stdnse.debug1("No response to NTLM challenge")
110:	    return nil

Version


This page has been created based on Nmap version 7.92.

Go back to menu.