Nmap imap-capabilities NSE Script

Script Overview

---

Script source code: https://github.com/nmap/nmap/tree/master/scripts/imap-capabilities.nse
Script categories: default, safe
Target service / protocol: imap, imaps
Target network port(s): 143, 993
List of CVEs: -

Script Description

---

The imap-capabilities.nse script retrieves IMAP email server capabilities.

IMAP4rev1 capabilities are defined in RFC 3501. The CAPABILITY command allows a client to ask a server what commands it supports and possibly any site-specific policy.

Imap-capabilities NSE Script Arguments

---

This is a full list of arguments supported by the imap-capabilities.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.

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

Imap-capabilities NSE Script Example Usage

---

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

nmap --script=imap-capabilities <target>

Imap-capabilities NSE Script Example Output

---

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

143/tcp open  imap
|_ imap-capabilities: LOGINDISABLED IDLE IMAP4 LITERAL+ STARTTLS NAMESPACE IMAP4rev1

Imap-capabilities 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

---

• Brandon Enright

References

---

• https://nmap.org/nsedoc/scripts/imap-capabilities.html
• https://github.com/nmap/nmap/tree/master/scripts/imap-capabilities.nse

See Also

---

Related NSE scripts to the imap-capabilities.nse script:

• imap-brute.nse
• imap-ntlm-info.nse

Visit Nmap NSE Library for more scripts.

The imap-capabilities.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 connect to server

---

Here is a relevant code snippet related to the "Failed to connect to server" error message:

28:	local function fail (err) return stdnse.format_output(false, err) end
29:	
30:	action = function(host, port)
31:	  local helper = imap.Helper:new(host, port)
32:	  local status = helper:connect()
33:	  if ( not(status) ) then return fail("Failed to connect to server") end
34:	
35:	  local status, capa = helper:capabilities(host, port)
36:	  if( not(status) ) then return fail("Failed to retrieve capabilities") end
37:	  helper:close()
38:	

Failed to retrieve capabilities

---

Here is a relevant code snippet related to the "Failed to retrieve capabilities" error message:

31:	  local helper = imap.Helper:new(host, port)
32:	  local status = helper:connect()
33:	  if ( not(status) ) then return fail("Failed to connect to server") end
34:	
35:	  local status, capa = helper:capabilities(host, port)
36:	  if( not(status) ) then return fail("Failed to retrieve capabilities") end
37:	  helper:close()
38:	
39:	  if type(capa) == "table" then
40:	    -- Convert the capabilities table into an array of strings.
41:	    local capstrings = {}