Nmap riak-http-info NSE Script


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

Script Description

The riak-http-info.nse script retrieves information (such as node name and architecture) from a Basho Riak distributed database using the HTTP protocol.

Riak-http-info NSE Script Arguments

This is a full list of arguments supported by the riak-http-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=riak-http-info --script-args smbdomain=value,smbhash=value <target>

Riak-http-info NSE Script Example Usage

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

nmap -p 8098 <ip> --script riak-http-info

Riak-http-info NSE Script Example Output

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

PORT     STATE SERVICE
8098/tcp open  http
| riak-http-info:
|   Node name                  [email protected]
|   Architecture               x86_64-unknown-linux-gnu
|   Storage backend            riak_kv_bitcask_backend
|   Total Memory               516550656
|   Crypto version             2.0.3
|   Skerl version              1.1.0
|   OS mon. version            2.2.6
|   Basho version              1.0.1
|   Lager version              0.9.4
|   Cluster info version       1.2.0
|   Luke version               0.2.4
|   SASL version               2.1.9.4
|   System driver version      1.5
|   Bitcask version            1.3.0
|   Riak search version        1.0.2
|   Riak kernel version        2.14.4
|   Riak stdlib version        1.17.4
|   Basho metrics version      1.0.0
|   WebMachine version         1.9.0
|   Public key version         0.12
|   Riak vore version          1.0.2
|   Riak pipe version          1.0.2
|   Runtime tools version      1.8.5
|   SSL version                4.1.5
|   MochiWeb version           1.5.1
|   Erlang JavaScript version  1.0.0
|   Riak kv version            1.0.2
|   Luwak version              1.1.2
|   Merge index version        1.0.1
|   Inets version              5.6
|_  Riak sysmon version        1.0.0

Riak-http-info 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

  • Patrik Karlsson

References

See Also

Visit Nmap NSE Library for more scripts.

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

Failed to parse response

Here is a relevant code snippet related to the "Failed to parse response" error message:

127:	    return
128:	  end
129:	
130:	  local status, parsed = json.parse(response.body)
131:	  if ( not(status) ) then
132:	    return fail("Failed to parse response")
133:	  end
134:	
135:	  local result = tab.new(2)
136:	  for _, item in ipairs(order) do
137:	    if ( parsed[item] ) then

Version

This page has been created based on Nmap version 7.92.

Go back to menu.