Nmap http-default-accounts NSE Script


This page contains detailed information about how to use the http-default-accounts 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/http-default-accounts.nse
Script categories: discovery, auth, intrusive
Target service / protocol: http, https
Target network port(s): 80, 443, 631, 7080, 8080, 8443, 8088, 5800, 3872, 8180, 8000
List of CVEs: -

Script Description

The http-default-accounts.nse script tests for access with default credentials used by a variety of web applications and devices.

It works similar to http-enum, we detect applications by matching known paths and launching a login routine using default credentials when found. This script depends on a fingerprint file containing the target's information: name, category, location paths, default credentials and login routine.

You may select a category if you wish to reduce the number of requests. We have categories like:

  • web - Web applications
  • routers - Routers
  • security - CCTVs and other security devices
  • industrial - Industrial systems
  • printer - Network-attached printers and printer servers
  • storage - Storage devices
  • virtualization - Virtualization systems
  • console - Remote consoles

You can also select a specific fingerprint or a brand, such as BIG-IQ or Siemens. This matching is based on case-insensitive words. This means that "nas" will select Seagate BlackArmor NAS storage but not Netgear ReadyNAS.

For a fingerprint to be used it needs to satisfy both the category and name criteria.

By default, the script produces output only when default credentials are found, while staying silent when the target only matches some fingerprints (but no credentials are found). With increased verbosity (option -v), the script will also report all matching fingerprints.

Please help improve this script by adding new entries to nselib/data/http-default-accounts.lua

Remember each fingerprint must have:

  • name - Descriptive name
  • category - Category
  • login_combos - Table of login combinations
  • paths - Table containing possible path locations of the target
  • login_check - Login function of the target

In addition, a fingerprint should have:

  • target_check - Target validation function. If defined, it will be called to validate the target before attempting any logins.
  • cpe - Official CPE Dictionary entry (see https://nvd.nist.gov/cpe.cfm)

Default fingerprint file: /nselib/data/http-default-accounts-fingerprints.lua This script was based on http-enum.

Http-default-accounts NSE Script Arguments

This is a full list of arguments supported by the http-default-accounts.nse script:

http-default-accounts.basepath

Base path to append to requests. Default: "/"

http-default-accounts.category

Selects a fingerprint category (or a list of categories).

http-default-accounts.fingerprintfile

Fingerprint filename. Default: http-default-accounts-fingerprints.lua

http-default-accounts.name

Selects fingerprints by a word (or a list of alternate words) included in their names.

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

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=http-default-accounts --script-args http-default-accounts.basepath=value,http-default-accounts.category=value <target>

Http-default-accounts NSE Script Example Usage

Here's an example of how to use the http-default-accounts.nse script:

nmap -p80 --script http-default-accounts host/ip

Http-default-accounts NSE Script Example Output

Here's a sample output from the http-default-accounts.nse script:

PORT   STATE SERVICE
80/tcp open  http
| http-default-accounts:
|   [Cacti] at /
|     admin:admin
|   [Nagios] at /nagios/
|_    nagiosadmin:CactiEZ

Http-default-accounts NSE Script Example XML Output

Here's a sample XML output from the http-default-accounts.nse script produced by providing the -oX <file> Nmap option:

 <table key="Cacti">
   <elem key="cpe">cpe:/a:cacti:cacti</elem>
   <elem key="path">/</elem>
   <table key="credentials">
     <table>
       <elem key="username">admin</elem>
       <elem key="password">admin</elem>
     </table>
   </table>
 </table>
 <table key="Nagios">
   <elem key="cpe">cpe:/a:nagios:nagios</elem>
   <elem key="path">/nagios/</elem>
   <table key="credentials">
     <table>
       <elem key="username">nagiosadmin</elem>
       <elem key="password">CactiEZ</elem>
     </table>
   </table>
 </table>

Authors

References

See Also

Visit Nmap NSE Library for more scripts.

The http-default-accounts.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.

Invalid path found in fingerprint entry #

Here is a relevant code snippet related to the "Invalid path found in fingerprint entry #" error message:

128:	    end
129:	    -- Validate paths
130:	    if(not(fingerprint.paths) or
131:	      (type(fingerprint.paths) ~= 'table' and type(fingerprint.paths) ~= 'string') or
132:	      (type(fingerprint.paths) == 'table' and #fingerprint.paths == 0)) then
133:	      return "Invalid path found in fingerprint entry #" .. i
134:	    end
135:	    if(type(fingerprint.paths) == 'string') then
136:	      fingerprint.paths = {fingerprint.paths}
137:	    end
138:	    for i, path in pairs(fingerprint.paths) do

Missing or invalid login_check function in entry #

Here is a relevant code snippet related to the "Missing or invalid login_check function in entry #" error message:

162:	      end
163:	    end
164:	
165:	     -- Make sure they include the login function
166:	    if(type(fingerprint.login_check) ~= "function") then
167:	      return "Missing or invalid login_check function in entry #"..i
168:	    end
169:	     -- Make sure that the target validation is a function
170:	    if(fingerprint.target_check and type(fingerprint.target_check) ~= "function") then
171:	      return "Invalid target_check function in entry #"..i
172:	    end

Invalid target_check function in entry #

Here is a relevant code snippet related to the "Invalid target_check function in entry #" error message:

166:	    if(type(fingerprint.login_check) ~= "function") then
167:	      return "Missing or invalid login_check function in entry #"..i
168:	    end
169:	     -- Make sure that the target validation is a function
170:	    if(fingerprint.target_check and type(fingerprint.target_check) ~= "function") then
171:	      return "Invalid target_check function in entry #"..i
172:	    end
173:	      -- Are they missing any fields?
174:	    if(fingerprint.category and type(fingerprint.category) ~= "string") then
175:	      return "Missing or invalid category in entry #"..i
176:	    end

Missing or invalid category in entry #

Here is a relevant code snippet related to the "Missing or invalid category in entry #" error message:

170:	    if(fingerprint.target_check and type(fingerprint.target_check) ~= "function") then
171:	      return "Invalid target_check function in entry #"..i
172:	    end
173:	      -- Are they missing any fields?
174:	    if(fingerprint.category and type(fingerprint.category) ~= "string") then
175:	      return "Missing or invalid category in entry #"..i
176:	    end
177:	    if(fingerprint.name and type(fingerprint.name) ~= "string") then
178:	      return "Missing or invalid name in entry #"..i
179:	    end
180:	  end

Missing or invalid name in entry #

Here is a relevant code snippet related to the "Missing or invalid name in entry #" error message:

173:	      -- Are they missing any fields?
174:	    if(fingerprint.category and type(fingerprint.category) ~= "string") then
175:	      return "Missing or invalid category in entry #"..i
176:	    end
177:	    if(fingerprint.name and type(fingerprint.name) ~= "string") then
178:	      return "Missing or invalid name in entry #"..i
179:	    end
180:	  end
181:	end
182:	
183:	-- Simplify unlocking the mutex, ensuring we don't try to load the fingerprints

Version

This page has been created based on Nmap version 7.92.

Go back to menu.