Nmap traceroute-geolocation NSE Script


This page contains detailed information about how to use the traceroute-geolocation 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/traceroute-geolocation.nse
Script categories: safe, external, discovery
Target service / protocol: -
Target network port(s): -
List of CVEs: -

Script Description

The traceroute-geolocation.nse script lists the geographic locations of each hop in a traceroute and optionally saves the results to a KML file, plottable on Google earth and maps.

Traceroute-geolocation NSE Script Arguments

This is a full list of arguments supported by the traceroute-geolocation.nse script:

traceroute-geolocation.kmlfile

Full path and name of file to write KML data to. The KML file can be used in Google earth or maps to plot the traceroute data.

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=traceroute-geolocation --script-args traceroute-geolocation.kmlfile=value,smbdomain=value <target>

Traceroute-geolocation NSE Script Example Usage

Here's an example of how to use the traceroute-geolocation.nse script:

nmap --traceroute --script traceroute-geolocation

Traceroute-geolocation NSE Script Example Output

Here's a sample output from the traceroute-geolocation.nse script:

| traceroute-geolocation:
|   hop  RTT     ADDRESS                                               GEOLOCATION
|   1    ...
|   2    ...
|   3    ...
|   4    ...
|   5    16.76   e4-0.barleymow.stk.router.colt.net (194.68.128.104)   62,15 Sweden (Unknown)
|   6    48.61   te0-0-2-0-crs1.FRA.router.colt.net (212.74.65.49)     54,-2 United Kingdom (Unknown)
|   7    57.16   87.241.37.146                                         42,12 Italy (Unknown)
|   8    157.85  212.162.64.146                                        42,12 Italy (Unknown)
|   9    ...
|_  10   ...

Traceroute-geolocation NSE Script Example XML Output

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

 <table>
   <elem key="hop">1</elem>
 </table>
 <table>
   <elem key="hop">2</elem>
 </table>
 <table>
   <elem key="hop">3</elem>
 </table>
 <table>
   <elem key="hop">4</elem>
 </table>
 <table>
   <elem key="hop">5</elem>
   <elem key="rtt">16.76</elem>
   <elem key="ip">194.68.128.104</elem>
   <elem key="hostname">e4-0.barleymow.stk.router.colt.net</elem>
   <elem key="lat">62</elem>
   <elem key="lon">15</elem>
 </table>
 <table>
   <elem key="hop">6</elem>
   <elem key="rtt">48.61</elem>
   <elem key="ip">212.74.65.49</elem>
   <elem key="hostname">te0-0-2-0-crs1.FRA.router.colt.net</elem>
   <elem key="lat">54</elem>
   <elem key="lon">-2</elem>
 </table>

Author

  • Patrik Karlsson

References

See Also

Visit Nmap NSE Library for more scripts.

The traceroute-geolocation.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 create KML file

Here is a relevant code snippet related to the "Failed to create KML file" error message:

118:	    output[#output+1] = ("%s,%s, 0.\r\n"):format(coord.lon, coord.lat)
119:	  end
120:	
121:	  local f = io.open(filename, "w")
122:	  if ( not(f) ) then
123:	    return false, "Failed to create KML file"
124:	  end
125:	  f:write(header .. table.concat(output) .. footer)
126:	  f:close()
127:	
128:	  return true

nnERROR: Failed to write KML to file: %s

Here is a relevant code snippet related to the "nnERROR: Failed to write KML to file: %s" error message:

177:	
178:	  if (#output_structured > 0) then
179:	    output = tab.dump(output)
180:	    if ( arg_kmlfile ) then
181:	      if ( not(createKMLFile(arg_kmlfile, coordinates)) ) then
182:	        output = output .. ("\n\nERROR: Failed to write KML to file: %s"):format(arg_kmlfile)
183:	      end
184:	    end
185:	    return output_structured, stdnse.format_output(true, output)
186:	  end
187:	end

Version

This page has been created based on Nmap version 7.92.

Go back to menu.