View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003706||Kali Linux||Kali Package Bug||public||2016-11-02 19:01||2020-12-01 10:48|
|Fixed in Version||2017.1|
|Summary||0003706: latest updates has caused nmap to drop high level of probes|
After running the latest update, regardless of the scan type I use, nmap will identify some open ports, then begin reporting it is dropping probes. Scans that usually take 30 seconds take over an hour. This happens regardless of scan target.
|Steps To Reproduce|
Took a backup of a Kali VM on a different computer, ran the update and attempted a scan. Probes were quickly dropped. Reverted back to the copy before the update and ran the nmap scan again and it was fine. Co-worker went through the same process and had the same result.
nmap -vv -p- <IP>
Starting Nmap 7.31 ( https://nmap.org ) at 2016-11-02 14:57 EDT
dpkg --list nmap
I made some tries and reverting to an older version of nmap did not help. Maybe it's kernel related?
What nmap and kernel versions did you have in your last working configuration? Can you try upgrading nmap without upgrading the kernel to confirm that the problem is not at the nmap level? Conversely, can you try upgrading the kernel and see if it introduces the problem?
In my test VM, I can reproduce the problem with nmap 1.30-0kali1 (so old version of nmap) with kernel 4.7.5-1kali1.
In fact, this does not look like a recent regression. Using ISO of Kali 2016.2 I can reproduce the same "problem" (so with nmap 7.25~BETA1-0kali1 and Linux 4.6.4-1kali1).
Problem also reproducible on Kali 2016.1 with nmap 7.01-1 and Linux 4.3.3-5kali4.
working fine with this kernel:
and this nmap:
which is latest nmap
on the other system which has the problem, everything is the same except the kernel:
and nmap is:
so it is either kernel, or nmap-libpcap-1.7.4 that breaks it.
If you look at http://pkg.kali.org/pkg/nmap you will see that we only had a single version of nmap 7.30 (aka 7.30-0kali1), so it's not possible that you got two different versions from Kali...
So what package version number do you have in both your cases?
Print "dpkg -s nmap" to find it out ("Version" field).
Difference is working one requires libpcap0.8 (>= 0.9.8) and the version is different
We uploaded a test version in kali experimental. Please test this package and let us know if it works better for you:
ShellStorm, can you please test the package at http://http.kali.org/pool/main/n/nmap/nmap_7.31-0kali3_amd64.deb and let us know if it works better for you?
New nmap package fixed the issue. Thank you!
new version 7.31-0kali3 is in kali-rolling
|2016-11-02 19:01||ShellStorm||New Issue|
|2016-11-02 19:09||ShellStorm||Note Added: 0006093|
|2016-11-02 21:54||rhertzog||Assigned To||=> sbrun|
|2016-11-02 21:54||rhertzog||Status||new => assigned|
|2016-11-02 22:31||rhertzog||Note Added: 0006096|
|2016-11-02 22:38||rhertzog||Note Added: 0006097|
|2016-11-02 22:44||rhertzog||Note Added: 0006098|
|2016-11-03 13:25||ShellStorm||Note Added: 0006100|
|2016-11-03 13:42||rhertzog||Note Added: 0006101|
|2016-11-03 14:00||ShellStorm||Note Added: 0006102|
|2016-11-04 13:44||sbrun||Note Added: 0006104|
|2016-11-07 22:34||rhertzog||Status||assigned => feedback|
|2016-11-07 22:34||rhertzog||Note Added: 0006107|
|2016-11-09 13:49||ShellStorm||Note Added: 0006109|
|2016-11-09 13:49||ShellStorm||Status||feedback => assigned|
|2016-11-10 08:58||sbrun||Status||assigned => resolved|
|2016-11-10 08:58||sbrun||Resolution||open => fixed|
|2016-11-10 08:58||sbrun||Fixed in Version||=> 2017.1|
|2016-11-10 08:58||sbrun||Note Added: 0006110|
|2020-12-01 10:48||g0tmi1k||Priority||high => normal|