1
0
mirror of https://github.com/nmap/nmap.git synced 2025-12-10 09:49:05 +00:00

Avoid assertion failure when unsolicited ARP response received

We probably want a more explicit handling of the case where we get an
ARP response to a request that we did not send (system's own, or another
Nmap scan running at the same time). In any case, this ought to solve
the crashes reported as #1797 and #1764.
This commit is contained in:
dmiller
2019-12-03 17:04:13 +00:00
parent e7e7e9e8c7
commit 33f421fd6e

View File

@@ -1275,9 +1275,14 @@ int UltraScanInfo::removeCompletedHosts() {
}
if (timedout)
gstats->num_hosts_timedout++;
/* We may have received an ARP response before we sent a probe, which
* would mean the timeout clock is not running. Avoid an assertion
* failure here by checking first. */
if (hss->target->timeOutClockRunning()) {
hss->target->stopTimeOutClock(&now);
}
}
}
return hostsRemoved;
}