Nmap 7.91 released: Bugfix
nmap (“Network Mapper“) is an open-source tool for network exploration and security auditing. It was designed to rapidly scan large networks, although it works fine to scan single hosts. nmap uses raw IP packets in novel ways to determine what hosts are available on the network, what services (application name and version) those hosts are offering, what operating systems (and OS versions) they are running, what type of packet filters/firewalls are in use, and dozens of other characteristics. While nmap is commonly used for security audits, many systems and network administrators find it useful for routine tasks such as network inventory, managing service upgrade schedules, and monitoring host or service uptime.
The output from nmap is a list of scanned targets, with supplemental information on each depending on the options used. Key among that information is the “interesting ports table”. That table lists the port number and protocol, service name, and state. The state is either open, filtered, closed, or unfiltered.
- Open means that an application on the target machine is listening for connections/packets on that port.
- 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.
- Closed ports have no application listening on them, though they could open up at any time. Ports are classified as unfiltered. when they are responsive to nmap’s probes, but nmap cannot determine whether they are open or closed. nmap reports the state combinations open|filtered and closed|filtered when it cannot determine which of the two states describe a port. The port table may also include software version details when version detection has been requested. When an IP protocol scan is requested (-sO), nmap provides information on supported IP protocols rather than listening ports.
In addition to the interesting ports table, nmap can provide further information on targets, including reverse DNS names, operating system guesses, device types, and MAC addresses.
Changelog Nmap 7.91:
– Fixed the “time result cannot be represented in this installation” crash, which occurred during many script scans (including -A) on Windows if the user was in a time zone after Coordinated Universal Time (e.g. UTC+X timezones). See https://issues.nmap.org/2136 [Clément Notin, nnposter, and Daniel Miller]
– Fixed a crash in the Zenmap GUI when using the profile editor. See https://issues.nmap.org/2148 [Dan Miller]
– Switched the default Windows I/O engine back to poll due to some problems with our IOCP engine that we need to work out. See https://issues.nmap.org/2139 [Dan Miller]
– Fix server response parsing in MySQL library to prevent certain script crashes. See https://issues.nmap.org/2128 [nnposter]