nmap crashes when scanning /24 subnet

Bug #1947165 reported by Joshua Smith
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nmap (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Using Ubuntu 21.04 on bare metal. When attempting to perform a scan of an entire subnet, I receive the following error:

sudo nmap -sn 192.168.0.1/24
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-14 10:14 EDT
nmap: Target.cc:503: void Target::stopTimeOutClock(const timeval*): Assertion `htn.toclock_running == true' failed.
Aborted

However, if I specify a smaller range, the scan is successful:

sudo nmap -sn 192.168.0.1-30
Starting Nmap 7.80 ( https://nmap.org ) at 2021-10-14 10:14 EDT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0071s latency).
MAC Address: XXXXXX (XXXXXX)
Nmap scan report for 192.168.0.26
Host is up (0.047s latency).
MAC Address: XXXXXX (XXXXXX)
Nmap done: 30 IP addresses (2 hosts up) scanned in 1.15 seconds

Adding --min-parallelism=100 also results in a successful scan on the entire subnet.

apt-cache policy nmap
nmap:
  Installed: 7.91+dfsg1+really7.80+dfsg1-1
  Candidate: 7.91+dfsg1+really7.80+dfsg1-1
  Version table:
 *** 7.91+dfsg1+really7.80+dfsg1-1 500
        500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages
        100 /var/lib/dpkg/status

nmap -V
Nmap version 7.80 ( https://nmap.org )
Platform: x86_64-pc-linux-gnu
Compiled with: liblua-5.3.3 openssl-1.1.1f nmap-libssh2-1.8.2 libz-1.2.11 libpcre-8.39 libpcap-1.10.0 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select

Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Hello,

Thanks for taking the time to file the bug and help in making Ubuntu Server better.

What you report has been reported upstream already via https://github.com/nmap/nmap/issues/1764. As per the comments, it is fixed via https://github.com/nmap/nmap/commit/33f421fd6e68fcb8ed50071661d9704717c81b2b.

The Ubuntu nmap package is in sync with the Debian package (https://tracker.debian.org/pkg/nmap). Can you perhaps open a bug there? So that once the bug is fixed there, it'll automatically be synced here as well? Thanks in advance! \o/

Changed in nmap (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Wladimir Mutel (mwg) wrote :

Still observing this bug with nmap 7.91+dfsg1+really7.80+dfsg1-2build1 in Ubuntu Jammy (22.04) LTS
Any chances to get it fixed by Apr 2024 ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.