It's a tool used for portscanning and this post will explore some of the common and useful flags that can be used while scanning to pick up usful information about targets.
What Is NMAP?
Nmap or Network mapper is an open source tool for network discovery and security analysis. It is used by many people in different job roles, from system administrators to penetration testers to developers and everyone inbetween. The primary uses are network discovery and analysis.
Nmap uses raw IP packets to determine what hosts are available on a network,it can also be used to identify what services (application name and version), operating system verions, what filters/firewalls are in use, and dozens of other characteristics.
Nmap runs on all major computer operating systems, and official binary packages are available for Linux, Windows, and Mac OS X. Typically nmap is used on the command line by calling
nmap however there is also a GUI available in the form of
In addition to the core tooling the nmap suite also includes a netcat-like tool on steroids(ncat), scan results comparison (Ndiff), and a packet generation and response analysis tool (Nping).
Port scanning is the act systematically scanning a computer's ports/services. Since a port is a place where information goes in and out of a computer, port scanning identifies openings into a computer. Port scanning has legitimate uses in managing networks, system administration and other network based tasks. However it can also be malicious in nature if someone is looking for a weakened access point to break into a system.
Typically it is one of the first techniques used to identify weaknesses or footholds into a network. One thing to note though is that the act of port scanning does fall under active recon and will send traffic to a target rather than passive scanning using things like OSINT.
Before we dive into the different flags, it is worth understanding that when scanning a port can have three states and depending on the scan type will depend on why the state has been returned. The main three are:
Open: Open means that an application or service is listening for connections or traffic on the on the target system.
Closed: Closed ports have no application listening on them. Ports are classified as unfiltered when they are responsive to Nmap's probes, but Nmap cannot determine whether they are open or closed.
Filtered: Filtered means that a firewall, filter, or other network obstacle is blocking the port so that Nmap cannot tell whether it is open or closed.
Nmap reports other state combinations such as
closed|filtered when it cannot determine which of the two states describe a port.
Some Common Commands
Nmap is one of the most used tools when carrying out infrastructure-like engagements. As such there are many different flags and command combinations that can be used to identify weaknesses and interesting information about hosts. The following sets of commands can be used to scan different types of hosts, each flag is explained and has been tuned for maximum performance.
Basic Scanning Options
There are three fairly commmon flags used in nmap for types of scanning, these are TCP connect scans, SYN & UDP. The flags for thes are shown below and a brief explanation of how they work is included too:
-sT: TCP connect scan is the default TCP scan type when SYN scan is not an option. This is selected when a user doesn't have elevate priveleges on a machine and therefore does not have permission to send raw packets or is scanning IPv6 networks. Instead of writing raw packets as most other scan types do, Nmap asks the underlying operating system to establish a connection with the target machine and port by issuing the connect system call and a TCP three way handshake. This is the same high-level system call that web browsers, P2P clients, and most other network-enabled applications use to establish a connection.
-sS: This flag is a SYN scan and it is the default, most popular scan option when using nmap. It can be performed quickly, scanning thousands of ports per second on a fast network or modern network. SYN scaning is relatively unobtrusive and stealthy, since it does not complete the TCP handshake, rather it sends syn and waits for a syn-ack response. Based on the response the port will then come back as either open, closed or filtered:
|Probe Response||Assigned State|
|TCP SYN/ACK response||
|TCP RST response||
|No response received or ICMP unreachable errors||
-sU: UDP scan works by sending a UDP packet to every targeted port. For most ports, this packet will be empty (no payload), but for a few of the more common ports a protocol-specific payload will be sent. Based on the response, or lack thereof, the port is assigned to one of four states as detailed in the table below:
|Probe Response||Assigned State|
|Any UDP response from target port||
|No response received after retransmission||
|ICMP port unreachable error (type 3, code 3)||
|Other ICMP unreachable errors (type 3, code 1, 2, 9, 10, or 13)||
-sV: Version scan, this will probe specific services and try to identifiy what version of a particular application or service is running on that port.
-O: OS Scan, this will send additional probes in order to determine what operating system the host is likely running.
There are so many different options when it comes to probing a service however here are some of the specifics when it comes to probing things.
-Pn: Don't ping the host, assume it's up - this is useful for hosts that don't respond to or block ping requests.
-PB: Default probing, scan port 80,443 and send an ICMP to the target.
-PE: Use a default ICMP echo request to probe a target
-PP: Use an ICMP timestamp request
-PM: Use an ICMP network request
Default Timing Options (
Sometimes when tuning a scan you might want to have certain options set to speed up or slow down scanning depending on if you want to be noisy or stealthy!
-T5: Insane; Very aggressive timing options, gotta go fast! This will likely crash unstable networks so shy away from it, in some instances it will also miss open ports due to the level of aggression.
-T4: Aggressive; Assumes a stable network, may overwhelm some networks if not setup to cope.
-T3: Normal; A dynamic timing mode which is based on how responsive the target is.
-T2: Polite; Slows down to consume less bandwidth, runs roughly ten times slower than a normal scan.
-T1: Sneaky; Quite slow, used to evade IDS and stay quiet on a network
-T0: Paranoid; Very slow, used to evade IDS and stay almost silent on a network.
In addition to these options you can fine tune a scan even more with the particular settings most people use these options to speed nmap up, but they can also be useful for slowing Nmap down. Often people will do that to evade IDS systems, reduce network load, or even improve accuracy if network conditions are so bad that even nmap's conservative default is too aggressive., these flags are detailed in the following table:
|Size of the group of hosts to be scanned concurrently||
|Number of scanning probes to be launched in parallel||
|Timeout values for probes||
|Maximum number of probe retransmissions allowed||
|Maximum time before giving up on an entire host||
|Control the delay inserted between each probe against an individual host||
|Rate of probe packets sent per second||
|Defeat RST packet response rate by target hosts||
Viewing the output in realtime can be useful however parsing the information afterwards and feeding it into other tools is 10x more useful. Enter the different output options from nmap, saving to a file of one sort or another.
There's a few options to output to but mainly these are xml,gnmap & nmap and have the flags;
-oN but there is also an easter egg output in 1337 speak which is
-oX: This instructs nmap to give the output in XML format for parsing later.
- Basic example:
nmap 10.0.0.1 -oX outFile
- Basic example:
-oG: To do the same thing for a grepable file,
-oGcan be used. If I wanted to pull up the text from that file, I can use: grep
HTTPSoutput.gnmap. This will search that file for the phrase
HTTPSand output the result.
- Basic example:
nmap 10.0.0.1 -oG outFile
- Basic example:
.nmapoutput will be the same as what is shown in realtime when you're running a scan, it allows you to quickly identify open ports or the bigger picture about a target.
- Basic example:
nmap 10.0.0.1 -oN outFile
- Basic example:
-oS: This option serves no real value over the past three however will output the results in a leet speak format for a bit of fun.
-oA: Lastly to output to all the formats previously mentioned (
.xml) just give it a name and you're away.
- Basic example:
nmap 10.0.0.1 -oA outFile
- Basic example:
Another useful output type is to view stats on the running scan. An example would be: nmap –stats-every 25s 10.0.0.1 to show me the statistical information every 25 seconds during a scan. You can use
s for seconds,
m for minutes, or
h for hours for this scan. This can be done to reduce the amount of info filling up a screen.
Scanning a single host for top 1000 open ports
nmap -sT <host> --top-ports 1000 -oA TCP-Top-1k
This command essentially does the following:
nmap: This is the name of the tool in use, nmap
-sT: This flag tells nmap to do a full TCP Connect scan against the target.
<host>: This is where the host goes either domain(blog.zsec.uk) or IP address(184.108.40.206)
--top-ports 1000: This tells nmap to scan the top 1000 ports which are:
if you're interested.
-oA: Output the results to
TCP-Top-1k: Name of output file
Some Options I Use
nmap -sSV -p- --min-parallelism 64 --min-hostgroup 16 --max-hostgroup 64 --max-retries 3 -Pn -n -iL input_hosts.txt -oA output --verson-all --reason
The different flags in this command do the following:
-sSV: This conducts a syn scan with version checks included.
-p-: Tells nmap to scan all
1 - 65535), if you want to include port
0you'll need to do
--min-parallelism 64: Launch 64 parallel tasks to probe the target.
--min-hostgroup 16: Scan a minimum of 16 hosts at one time and...
--max-hostgroup 64: ... a maximum amount of 64 hosts.
--max-retries 3: The amount of times to retry probing a port before moving onto the next service.
-Pn: Skip ping scans, assume the host is up.
-n: Skip dns resolution, usually select this when not interested in reverse dns or wanting a quicker scan :-).
-iL input_hosts.txt: Take an input file containing target hosts.
-oA output: Output the results to
.xmlfor parsing later and analysing.
--verson-all: Do extended version checks against the host to find out services running.
--reason: Detail the reason why a port is determined as open, filtered or closed.
Probing a specific service for more information and looking for known issues:
sudo nmap -sSV --version-all -p 11211 --min-parallelism 64 --script=vuln 10.0.0.1 -Pn -n
The addition of the
--script=vuln and specifc port tells nmap to only probe the port
11211 and tell me any vulnerable services it knows about running on that port. Additionally
-sC can be used to scan a target and probe with common scripts. More information on the scripting engine can be found below.
One final one-liner I use a lot is to get the output of a subnet mask, something like:
nmap -sL -n 10.10.10.1/24 | grep report | cut -d " " -f 5 >> ips.txt
This will simply print all of the hosts in the range given as individual IP addresses, very useful when you don't have a subnet calc on hand or want unique ips for other tools!
So going beyond normal scans, nmap does a lot more. It is capable of scanning IPv6 networks, has an inbuilt vulnerability scanning engine and can even be tuned to evade filtering. The next few subsections explain the different flags and features that can be leveraged to do these things.
I've covered scanning IPv6 before in my post about pwning ipv6 things which you can read here. However as a quick input the
--ipv6 flags will instruct nmap that you're scanning an IPv6 address. Typically using something like:
sudo nmap -6 -sSV -p- -iL targets.txt -oA example_IPv6 --version-all --max-retries 3 -T4 -Pn -n --reason –vvv
Will work no problem, the breakdown of this command is as follows:
-6: tells nmap that the targets are IPv6 hosts
-sSV: instructs nmap to carry out a syn half-open scan & a version scan
-p-: notes to scan all 65535 ports
-iL: This flag tells nmap to load targets from a file path, loads from the current folder.
-oA: notes the output to be in all three formats that nmap supports; XML, nmap & greppable nmap output.
--version-all: Sends additional version probes to attempt to discover the version of software running on each open port.
--max-retries: Notes the maximum amount of retries nmap will do per port
-T4: Adds additional timing options to nmap tuning the parallel processes and other timeout settings
-Pn: Instructs nmap to assume the host is up and not to send ICMP packets to the target.
-n: Tells nmap not to carry out DNS resolution of targets.
--reason: Tells nmap to show the reason why a port is determined as open or closed based upon response.
-vvv: This increases the verbosity of scan output.
Of course, you must use IPv6 syntax if you specify an address rather than a hostname. An address might look like 3ffe:7501:4819:2000:210:f3ff:fe03:14d0, so hostnames are recommended.
NSE - Nmap Scripting Engine
Most people reading this will have heard of metasploit framework(MSF), however a few may not realise that nmap has it's own vuln scanning ability built in. It's not a repacement for MSF but it has got some great features.
The NSE is a framework that runs code written in the programming language Lua with specific flags that the engine can parse. Lua is a lightweight, fast, and interpreted programming language.
I could write a whole article on itsown covering the NSE side of nmap as it is so vast and includes many many many different options. Here are a few basic ones to get you started:
-sC: This flag performs a script scan using the default set of scripts. It is equivalent to --script=default.
--script=vuln: This will run a select set of scripts looking for vulnerable software, read through the scripts it will run before running against a target to prevent unwanted outages.
--script=safe: This will instruct nmap to only run scripts it deems safe against the target, these are bundled to gether with the intention of information gathering rather than exploiting issues.
A full list of the main NSE scripts built into nmap can be found on the nmap site here.
Here are some options that you might not know about that will help you in evading firewall blockages;
-sA: TCP ACK Scan, this can be leveraged to find out if there is a firewall in place based on the response. It is always a good idea to send ACK packets rather than the SYN because if there is any active firewall working on the remote system then the firewall cannot create a log, since firewalls treat ACK packet as the response of the SYN packet.
-f: This option tells nmap to use fragmentation and the scan will use tiny fragmented IP packets. The idea behind this is to split up the TCP header over several packets to make it harder for packet filters, intrusion detection systems, and other annoyances to detect what you are doing. This is all find and well but be careful with this, as some programs have trouble handling these tiny packets and could cause an impact on the application or service.
--mtu 24: This flag can be used to set a specific MTU (Maximum Transmission Unit) to the packet. This is similar to packet fragmentation explained above. In the example given I have used the number 24 so the nmap will create 24-byte packets causing a confusion to the firewall. Bear in mind that the MTU number must be a multiple of 8 (8,16,24,32 etc).
-D RND:10: This flag indicates the random number of decoy packets to send with each request, in an attempt to bypass network filtering or firewalls. You can instruct Nmap to spoof packets from other hosts. In the firewall logs it will be not only our IP address but also and the IP addresses of the decoys so it will be much harder to determine which system initiated the scanning.There are two options that you can use in this type of scan:
nmap -D RND:10 10.0.0.1 (Generates a random number of decoys) nmap -D decoy1,decoy2,decoy3 etc. (Manually specify the IP addresses of the decoys)
It's also worth noting that the hosts being used as decoys must be online in order this technique to work.Also using many decoys can cause network congestion.
--source-port 80: One surprisingly common misconfiguration is to trust traffic based only on the source port number. This flag can be used to change source port to throw off the scent of scanning. Simply provide a port number, and Nmap will send packets from that port where possible. Nmap must use different port numbers for certain OS detection tests to work properly. Most TCP scans, including SYN scan, support the option completely, as does UDP scan.
--data-length 1337: Append Random Data to Packet for systems that use traffic shaping and other deep analysis.
--spoof-mac Dell/Apple/3Com: This flag can be used to spoof the mac address of your scanning machine, this can be useful to bypass network access control that is based on the mac address of systems connected into the network.
There are of course more options that can be leveraged to evade and bypass IDS/IPS/Firewalls however the above should be a good starter.
Other Tooling with NMAP
Port scanning is great but nmap also has a suite of other tools that can be used, here's a quick overview on how to use them and some common options to try.
ncat: Ncat is a re-invented version of netcat, it offers many more features over the standard netcat. It leverages both TCP and UDP for communication and was designed to be a reliable back-end tool to instantly provide network connectivity to other applications and users. It also works with both IPv4 and IPv6. In addition to this it also offers SSL support and proxying.
ndiff: Ndiff is a tool to carry out a comparison of Nmap scans. It takes two nmap xml output files and shows the differences between them.
nping: Nping is used for network packet generation, response analysis and response time measurement. It can generate raw network packets for various protocols. While Nping can be used as a simple ping utility to detect active hosts, it can also be used as a raw packet generator for network stack stress testing, ARP poisoning, Denial of Service attacks, route tracing and many more!
Here is a short explanation on how to compile nmap statically.
Version of nmap used: https://nmap.org/dist/nmap-7.70.tar.bz2
First set up the environment (''-fPIC'' is needed, for static compilation):
export CFLAGS="-march=core2 -O2 -fomit-frame-pointer -pipe -fPIC" export CXXFLAGS="-march=core2 -O2 -fomit-frame-pointer -pipe -fPIC"
Then run ./configure with minimal options:
./configure --without-subversion --without-liblua --without-zenmap --with-pcre=/usr --with-libpcap=included --with-libdnet=included --without-ndiff --without-nmap-update --without-ncat --without-liblua --without-nping --without-openssl
And compile - this will mostly work:
make -j4 static
The final compilation step fails - the actual error is:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.4/../../../../x86_64-unknown-linux-gnu/bin/ld: dynamic STT_GNU_IFUNC symbol `strcmp' with pointer equality in /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.4/../../../../lib/libc.a(strcmp.o)' can not be used when making an executable; recompile with -fPIE and relink with -pie
Making it Work
Hacking the Makefile, to make the compilation ''mostly'' static:
- Change the
LIBS = -lnsock -lnbase -lpcreline 54 to:
LIBS = -lnsock -lnbase $(LIBPCAPDIR)/libpcap.a $(OPENSSL_LIBS) libnetutil/libnetutil.a $(top_srcdir)/libdnet-stripped/src/.libs/libdnet.a $(top_srcdir)/liblinear/liblinear.a -ldl
$(CXX) $(LDFLAGS) -o [email protected] $(OBJS) $(LIBS)line 122 (under "Compiling nmap") to:
$(CXX) $(LDFLAGS) -o [email protected] $(OBJS) $(LIBS) /usr/lib/libpcre.a
And re-run the final compilation step:
This succeeds, and we have:
$ ldd nmap | cut -d '(' -f1 linux-vdso.so.1 libdl.so.2 => /usr/lib/libdl.so.2 libstdc++.so.6 => /usr/lib/libstdc++.so.6 libm.so.6 => /usr/lib/libm.so.6 libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 libc.so.6 => /usr/lib/libc.so.6 /lib64/ld-linux-x86-64.so.2
This is as ''static'' as the executable can be made, with
glibc - those are all links to glibc's libraries.