Nmap nexpose-brute NSE Script


This page contains detailed information about how to use the nexpose-brute 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/nexpose-brute.nse
Script categories: intrusive, brute
Target service / protocol: nexpose, tcp
Target network port(s): 3780
List of CVEs: -

Script Description

The nexpose-brute.nse script performs brute force password auditing against a Nexpose vulnerability scanner using the API 1.1.

As the Nexpose application enforces account lockout after 4 incorrect login attempts, the script performs only 3 guesses per default. This can be altered by supplying the brute.guesses argument a different value or 0 (zero) to guess the whole dictionary.

Nexpose-brute NSE Script Arguments

This is a full list of arguments supported by the nexpose-brute.nse script:

creds.global

Credentials to be returned by Credentials.getCredentials regardless of the service.

creds.[service]

Credentials to be returned by Credentials.getCredentials for [service]. E.g. creds.http=admin:password

passdb

The filename of an alternate password database. Default: nselib/data/passwords.lst

unpwdb.passlimit

The maximum number of passwords passwords will return (default unlimited).

unpwdb.timelimit

The maximum amount of time that any iterator will run before stopping. The value is in seconds by default and you can follow it with ms, s, m, or h for milliseconds, seconds, minutes, or hours. For example, unpwdb.timelimit=30m or unpwdb.timelimit=.5h for 30 minutes. The default depends on the timing template level (see the module description). Use the value 0 to disable the time limit.

unpwdb.userlimit

The maximum number of usernames usernames will return (default unlimited).

userdb

The filename of an alternate username database. Default: nselib/data/usernames.lst

brute.credfile

A file containing username and password pairs delimited by '/'

brute.delay

The number of seconds to wait between guesses (default: 0)

brute.emptypass

Guess an empty password for each user (default: false)

brute.firstonly

Stop guessing after first password is found (default: false)

brute.guesses

The number of guesses to perform against each account. (default: 0 (unlimited)). The argument can be used to prevent account lockouts.

brute.mode

Can be user, pass or creds and determines what mode to run the engine in.

  • user - the unpwdb library is used to guess passwords, every password Password is tried for each user. (The user iterator is in the outer loop)
  • pass - the unpwdb library is used to guess passwords, each password Is tried for every user. (The password iterator is in the outer loop)
  • creds - a set of credentials (username and password pairs) are Guessed against the service. This allows for lists of known or common username and password combinations to be tested. If no mode is specified and the script has not added any custom iterator the pass mode will be enabled.

brute.passonly

Iterate over passwords only for services that provide only a password for authentication. (default: false)

brute.retries

The number of times to retry if recoverable failures occur. (default: 2)

brute.start

The number of threads the engine will start with. (default: 5).

brute.threads

The number of initial worker threads, the number of active threads will be automatically adjusted.

brute.unique

Make sure that each password is only guessed once (default: true)

brute.useraspass

Guess the username as password for each user (default: true)

creds.[service]

Credentials to be returned by Credentials.getCredentials for [service]. E.g. creds.http=admin:password

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.

slaxml.debug

Debug level at which default callbacks will print detailed parsing info. Default: 3

http.host

The value to use in the Host header of all requests unless otherwise set. By default, the Host header uses the output of stdnse.get_hostname().

http.max-body-size

Limit the received body to specific number of bytes. An oversized body results in an error unless script argument http.truncated-ok or request option truncated_ok is set to true. The default is 2097152 (2MB). Use value -1 to disable the limit altogether. This argument can be overridden case-by-case with request option max_body_size.

http.max-cache-size

The maximum memory size (in bytes) of the cache.

http.max-pipeline

If set, it represents the number of outstanding HTTP requests that should be sent together in a single burst. Defaults to http.pipeline (if set), or to what function get_pipeline_limit returns.

http.pipeline

If set, it represents the number of HTTP requests that'll be sent on one connection. This can be set low to make debugging easier, or it can be set high to test how a server reacts (its chosen max is ignored).

http.truncated-ok

Do not treat oversized body as error. (Use response object flag truncated to check if the returned body has been truncated.) This argument can be overridden case-by-case with request option truncated_ok.

http.useragent

The value of the User-Agent header field sent with requests. By default it is "Mozilla/5.0 (compatible; Nmap Scripting Engine; https://nmap.org/book/nse.html)". A value of the empty string disables sending the User-Agent header field.

- - -
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=nexpose-brute --script-args creds.global=value,creds.\[service]=value <target>

Nexpose-brute NSE Script Example Usage

Here's an example of how to use the nexpose-brute.nse script:

nmap --script nexpose-brute -p 3780 <ip>

Nexpose-brute NSE Script Example Output

Here's a sample output from the nexpose-brute.nse script:

PORT     STATE SERVICE     REASON  VERSION
3780/tcp open  ssl/nexpose syn-ack NeXpose NSC 0.6.4
| nexpose-brute:
|   Accounts
|     nxadmin:nxadmin - Valid credentials
|   Statistics
|_    Performed 5 guesses in 1 seconds, average tps: 5

Nexpose-brute 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

  • Vlatko Kosturjak

References

See Also

Visit Nmap NSE Library for more scripts.

The nexpose-brute.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.

Couldn't send/receive HTTPS request

Here is a relevant code snippet related to the "Couldn't send/receive HTTPS request" error message:

53:	  login = function( self, username, password )
54:	    local postdata='<?xml version="1.0" encoding="UTF-8"?><LoginRequest sync-id="1" user-id="'..username..'" password="'..password..'"></LoginRequest>'
55:	    local response = http.post( self.host, self.port, '/api/1.1/xml', { no_cache = true, header = { ["Content-Type"] = "text/xml" } }, nil, postdata )
56:	
57:	    if (not(response)) then
58:	      local err = brute.Error:new( "Couldn't send/receive HTTPS request" )
59:	      err:setRetry( true )
60:	      return false, err
61:	    end
62:	
63:	    if (response.body == nil or response.body:match('<LoginResponse.*success="0"')) then

Bad login

Here is a relevant code snippet related to the "Bad login" error message:

60:	      return false, err
61:	    end
62:	
63:	    if (response.body == nil or response.body:match('<LoginResponse.*success="0"')) then
64:	      stdnse.debug2("Bad login: %s/%s", username, password)
65:	      return false, brute.Error:new( "Bad login" )
66:	    elseif (response.body:match('<LoginResponse.*success="1"')) then
67:	      stdnse.debug1("Good login: %s/%s", username, password)
68:	      return true, creds.Account:new(username, password, creds.State.VALID)
69:	    end
70:	    stdnse.debug1("WARNING: Unhandled response: %s", response.body)

WARNING: Unhandled response: %s

Here is a relevant code snippet related to the "WARNING: Unhandled response: %s" error message:

65:	      return false, brute.Error:new( "Bad login" )
66:	    elseif (response.body:match('<LoginResponse.*success="1"')) then
67:	      stdnse.debug1("Good login: %s/%s", username, password)
68:	      return true, creds.Account:new(username, password, creds.State.VALID)
69:	    end
70:	    stdnse.debug1("WARNING: Unhandled response: %s", response.body)
71:	    return false, brute.Error:new( "incorrect response from server" )
72:	  end,
73:	
74:	  disconnect = function( self ) return true end,
75:	}

incorrect response from server

Here is a relevant code snippet related to the "incorrect response from server" error message:

66:	    elseif (response.body:match('<LoginResponse.*success="1"')) then
67:	      stdnse.debug1("Good login: %s/%s", username, password)
68:	      return true, creds.Account:new(username, password, creds.State.VALID)
69:	    end
70:	    stdnse.debug1("WARNING: Unhandled response: %s", response.body)
71:	    return false, brute.Error:new( "incorrect response from server" )
72:	  end,
73:	
74:	  disconnect = function( self ) return true end,
75:	}
76:

Version

This page has been created based on Nmap version 7.92.

Go back to menu.