Nmap http-trane-info NSE Script


This page contains detailed information about how to use the http-trane-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/http-trane-info.nse
Script categories: discovery, version, safe
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-trane-info.nse script attempts to obtain information from Trane Tracer SC devices. Trane Tracer SC is an intelligent field panel for communicating with HVAC equipment controllers deployed across several sectors including commercial facilities and others.

The information is obtained from the web server that exposes sensitive content to unauthenticated users.

Tested on Trane Tracer SC version 4.40.1211 and below.

References:

Http-trane-info NSE Script Arguments

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

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

Http-trane-info NSE Script Example Usage

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

nmap -p80 --script trane-info.nse <target>

Http-trane-info NSE Script Example Output

Here's a sample output from the http-trane-info.nse script:

| http-trane-info:
|   serverName: XXXXX
|   serverTime: 2017-09-24T01:03:08-05:00
|   serverBootTime: 2017-08-03T02:06:39-05:00
|   vendorName: Trane
|   productName: Tracer SC
|   productVersion: v4.20.1128 (release)
|   kernelVersion: 2.6.30_HwVer12AB-hydra
|   hardwareType: HwVer12AB
|   hardwareSerialNumber: XXXXX
|   devices:
|
|       isOffline: false
|       equipmentUri: /equipment/dac/generic/1
|       displayName: RTU-01
|       equipmentFamily: AirHandler
|       roleDocument: BCI-I_9a8c9b8116cd392fc0b4a233405f3f5964fa6b885809c810a8d0ed5478XXXXXX__RTU_Ipak_VAV
|       deviceName: RTU-01

Http-trane-info NSE Script Example XML Output

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

 <elem key="serverName">XXXXX </elem>
 <elem key="serverTime">2017-09-24T01:05:28-05:00 </elem>
 <elem key="serverBootTime">2017-08-03T02:06:39-05:00 </elem>
 <elem key="vendorName">Trane </elem>
 <elem key="productName">Tracer SC </elem>
 <elem key="productVersion">v4.20.1128 (release) </elem>
 <elem key="kernelVersion">2.6.30_HwVer12AB-hydra </elem>
 <elem key="hardwareType">HwVer12AB </elem>
 <elem key="hardwareSerialNumber">XXXXX </elem>
 <table key="devices">
 <table>
 <elem key="equipmentUri">/equipment/dac/generic/1 </elem>
 <elem key="equipmentFamily">AirHandler </elem>
 <elem key="deviceName">RTU-01 </elem>
 <elem key="isOffline">false </elem>
 <elem key="roleDocument">BCI-I_9a8c9b8116cd392fc0b4a233405f3f5964fa6b885809c810a8d0ed5478XXXXX__RTU_Ipak_VAV </elem>
 <elem key="displayName">RTU-01 </elem>
 </table></table>

Author

  • Pedro Joaquin <pjoaquin()websec.mx>

References

See Also

Visit Nmap NSE Library for more scripts.

The http-trane-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.

Problem with XML parsing of /evox/about

Here is a relevant code snippet related to the "Problem with XML parsing of /evox/about" error message:

77:	  local response = http.get(host, port, uri)
78:	  if response['status-line'] and response['status-line']:match("200") then
79:	    --Verify parsing of XML from /evox/about
80:	    local deviceType = response['body']:match('serverName" val=([^<]*)/>')
81:	    if not deviceType then
82:	      stdnse.debug1("Problem with XML parsing of /evox/about")
83:	      return nil,"Problem with XML parsing of /evox/about"
84:	    end
85:	
86:	    --Parse information from /evox/about
87:	    local keylist = {"serverName","serverTime","serverBootTime","vendorName","productName","productVersion","kernelVersion","hardwareType","hardwareSerialNumber"}

Problem with XML parsing of /evox/about

Here is a relevant code snippet related to the "Problem with XML parsing of /evox/about" error message:

78:	  if response['status-line'] and response['status-line']:match("200") then
79:	    --Verify parsing of XML from /evox/about
80:	    local deviceType = response['body']:match('serverName" val=([^<]*)/>')
81:	    if not deviceType then
82:	      stdnse.debug1("Problem with XML parsing of /evox/about")
83:	      return nil,"Problem with XML parsing of /evox/about"
84:	    end
85:	
86:	    --Parse information from /evox/about
87:	    local keylist = {"serverName","serverTime","serverBootTime","vendorName","productName","productVersion","kernelVersion","hardwareType","hardwareSerialNumber"}
88:	    for _,key in ipairs(keylist) do

body']:match('Error code: 00017

Here is a relevant code snippet related to the "body']:match('Error code: 00017" error message:

97:	    --Get information from /evox/equipment/installedSummary
98:	    local uri = '/evox/equipment/installedSummary'
99:	    local response = http.get(host, port, uri)
100:	    if response['status-line'] and response['status-line']:match("200") then
101:	      --Verify parsing of XML from /evox/equipment/installedSummary
102:	      local error = response['body']:match('Error code: 00017')
103:	      if error then
104:	        stdnse.debug1("/evox/equipment/installedSummary is not available")
105:	      end
106:	      local equipmentUri = response['body']:match('equipmentUri" val=([^<]*)/>')
107:	      if not equipmentUri then

Problem with XML parsing

Here is a relevant code snippet related to the "Problem with XML parsing" error message:

103:	      if error then
104:	        stdnse.debug1("/evox/equipment/installedSummary is not available")
105:	      end
106:	      local equipmentUri = response['body']:match('equipmentUri" val=([^<]*)/>')
107:	      if not equipmentUri then
108:	        stdnse.debug1("Problem with XML parsing")
109:	      end
110:	      if not error then
111:	        --Parse information from /evox/equipment/installedSummary
112:	        local keylist = {"equipmentUri","displayName","deviceName","equipmentFamily","roleDocument","isOffline"}
113:	        local _,lastequipmentUri = response['body']:find(".*equipmentUri")

Request returned a network error.

Here is a relevant code snippet related to the "Request returned a network error." error message:

135:	    end
136:	  end
137:	  stdnse.debug2("status-line: "..response['status-line'])
138:	  local error = response['status-line']:match('Error')
139:	  if error then
140:	    stdnse.debug2("Request returned a network error.")
141:	    return nil, "Request returned a network error."
142:	  end
143:	
144:	  -- Set the port version
145:	  port.version.name = "http"

Request returned a network error.

Here is a relevant code snippet related to the "Request returned a network error." error message:

136:	  end
137:	  stdnse.debug2("status-line: "..response['status-line'])
138:	  local error = response['status-line']:match('Error')
139:	  if error then
140:	    stdnse.debug2("Request returned a network error.")
141:	    return nil, "Request returned a network error."
142:	  end
143:	
144:	  -- Set the port version
145:	  port.version.name = "http"
146:	  port.version.name_confidence = 10

Version

This page has been created based on Nmap version 7.92.

Go back to menu.