Nmap flume-master-info NSE Script
This page contains detailed information about how to use the flume-master-info NSE script. For list of all NSE scripts, visit the Nmap NSE Library.
Script Overview
Script source code: https://github.com/nmap/nmap/tree/master/scripts/flume-master-info.nse
Script categories: default, discovery, safe
Target service / protocol: flume-master
Target network port(s): 35871
List of CVEs: -
Script Description
The flume-master-info.nse script retrieves information from Flume master HTTP pages.
Information gathered:
- Flume version
- Flume server id
- Zookeeper/Hbase master servers present in configured flows
- Java information
- OS information
- various other local configurations.
If this script is run wth -v, it will output lots more info.
Use the newtargets
script argument to add discovered hosts to
the Nmap scan queue.
Flume-master-info NSE Script Arguments
This is a full list of arguments supported by the flume-master-info.nse script:
smbdomainThe domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.
smbhashA 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.
smbnoguestUse to disable usage of the 'guest' account.
smbpasswordThe 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.
smbtypeThe 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 usev2
orlmv2
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 tov1
orlm
, which are less secure but more compatible. For information, seesmbauth.lua
.
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.
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()
.
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
.
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.
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
.
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.
Sets the number of the maximum allowed new targets. If set to 0 or less then there is no limit. The default value is 0.
newtargetsIf specified, lets NSE scripts add new targets.
- - -
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=flume-master-info --script-args smbdomain=value,smbhash=value <target>
Flume-master-info NSE Script Example Usage
Here's an example of how to use the flume-master-info.nse script:
nmap --script flume-master-info -p 35871 host
Flume-master-info NSE Script Example Output
Here's a sample output from the flume-master-info.nse script:
PORT STATE SERVICE REASON
35871/tcp open flume-master syn-ack
| flume-master-info:
| Version: 0.9.4-cdh3u3
| ServerID: 0
| Flume nodes:
| node1.example.com
| node2.example.com
| node5.example.com
| node6.example.com
| node3.example.com
| node4.example.com
| Zookeeper Master:
| master1.example.com
| Hbase Master Master:
| hdfs://master1.example.com:8020/hbase
| Enviroment:
| java.runtime.name: Java(TM) SE Runtime Environment
| java.runtime.version: 1.6.0_36-a01
| java.version: 1.6.0_36
| java.vm.name: Java HotSpot(TM) 64-Bit Server VM
| java.vm.vendor: Sun Microsystems Inc.
| java.vm.version: 14.0-b12
| os.arch: amd64
| os.name: Linux
| os.version: 2.6.32-220.4.2.el6.x86_64
| user.country: US
| user.name: flume
| Config:
| dfs.datanode.address: 0.0.0.0:50010
| dfs.datanode.http.address: 0.0.0.0:50075
| dfs.datanode.https.address: 0.0.0.0:50475
| dfs.datanode.ipc.address: 0.0.0.0:50020
| dfs.http.address: master1.example.com:50070
| dfs.https.address: 0.0.0.0:50470
| dfs.secondary.http.address: 0.0.0.0:50090
| flume.collector.dfs.dir: hdfs://master1.example.com/user/flume/collected
| flume.collector.event.host: node1.example.com
| flume.master.servers: master1.example.com
| fs.default.name: hdfs://master1.example.com:8020
| mapred.job.tracker: master1.example.com:9001
| mapred.job.tracker.handler.count: 10
| mapred.job.tracker.http.address: 0.0.0.0:50030
| mapred.job.tracker.http.address: 0.0.0.0:50030
| mapred.job.tracker.jobhistory.lru.cache.size: 5
| mapred.job.tracker.persist.jobstatus.active: false
| mapred.job.tracker.persist.jobstatus.dir: /jobtracker/jobsInfo
| mapred.job.tracker.persist.jobstatus.hours: 0
| mapred.job.tracker.retiredjobs.cache.size: 1000
| mapred.task.tracker.http.address: 0.0.0.0:50060
|_ mapred.task.tracker.report.address: 127.0.0.1:0
Flume-master-info NSE Script Example XML Output
Here's a sample XML output from the flume-master-info.nse script produced by providing the -oX <file>
Nmap option:
<elem key="Version">0.9.4-cdh3u3</elem>
<elem key="ServerID">0</elem>
<table key="Flume nodes">
<elem>node1.example.com</elem>
<elem>node2.example.com</elem>
<elem>node5.example.com</elem>
<elem>node6.example.com</elem>
<elem>node3.example.com</elem>
<elem>node4.example.com</elem>
</table>
<table key="Zookeeper Master">
<elem>master1.example.com</elem>
</table>
<table key="Hbase Master Master">
<elem>hdfs://master1.example.com:8020/hbase</elem>
</table>
<table key="Enviroment">
<elem key="java.runtime.name">Java(TM) SE Runtime Environment</elem>
<elem key="java.runtime.version">1.6.0_36-a01</elem>
<elem key="java.version">1.6.0_36</elem>
<elem key="java.vm.name">Java HotSpot(TM) 64-Bit Server VM</elem>
<elem key="java.vm.vendor">Sun Microsystems Inc.</elem>
<elem key="java.vm.version">14.0-b12</elem>
<elem key="os.arch">amd64</elem>
<elem key="os.name">Linux</elem>
<elem key="os.version">2.6.32-220.4.2.el6.x86_64</elem>
<elem key="user.country">US</elem>
<elem key="user.name">flume</elem>
</table>
<table key="Config">
<elem key="dfs.datanode.address">0.0.0.0:50010</elem>
<elem key="dfs.datanode.http.address">0.0.0.0:50075</elem>
<elem key="dfs.datanode.https.address">0.0.0.0:50475</elem>
<elem key="dfs.datanode.ipc.address">0.0.0.0:50020</elem>
<elem key="dfs.http.address">master1.example.com:50070</elem>
<elem key="dfs.https.address">0.0.0.0:50470</elem>
<elem key="dfs.secondary.http.address">0.0.0.0:50090</elem>
<elem key="flume.collector.dfs.dir">hdfs://master1.example.com/user/flume/collected</elem>
<elem key="flume.collector.event.host">node1.example.com</elem>
<elem key="flume.master.servers">master1.example.com</elem>
<elem key="fs.default.name">hdfs://master1.example.com:8020</elem>
<elem key="mapred.job.tracker">master1.example.com:9001</elem>
<elem key="mapred.job.tracker.handler.count">10</elem>
<elem key="mapred.job.tracker.http.address">0.0.0.0:50030</elem>
<elem key="mapred.job.tracker.http.address">0.0.0.0:50030</elem>
<elem key="mapred.job.tracker.jobhistory.lru.cache.size">5</elem>
<elem key="mapred.job.tracker.persist.jobstatus.active">false</elem>
<elem key="mapred.job.tracker.persist.jobstatus.dir">/jobtracker/jobsInfo</elem>
<elem key="mapred.job.tracker.persist.jobstatus.hours">0</elem>
<elem key="mapred.job.tracker.retiredjobs.cache.size">1000</elem>
<elem key="mapred.task.tracker.http.address">0.0.0.0:50060</elem>
<elem key="mapred.task.tracker.report.address">127.0.0.1:0</elem>
</table>
Author
- John R. Bond
References
- https://nmap.org/nsedoc/scripts/flume-master-info.html
- https://github.com/nmap/nmap/tree/master/scripts/flume-master-info.nse
- https://nmap.org/svn/docs/licenses/BSD-simplified
- http://lua-users.org/wiki/TableUtils
See Also
Visit Nmap NSE Library for more scripts.
Version
This page has been created based on Nmap version 7.92.