2.3.5 Regression - Host Discovery Failing #1531
Description
Naabu Version
2.3.5
Current Behavior
Under 2.3.5, host discovery is failing:
user@user:~/source/proj $ sudo /apps/naabu-2.3.5 -host 192.168.1.0/28 -wn -sn -v
__
___ ___ ___ _/ / __ __
/ _ \/ _ \/ _ \/ _ \/ // /
/_//_/\_,_/\_,_/_.__/\_,_/
projectdiscovery.io
[INF] Current naabu version 2.3.5 (latest)
[WRN] host discovery requires syn scan, automatically switching to syn scan
[WRN] UI Dashboard is disabled, Use -dashboard option to enable
[INF] Running host discovery scan
Output terminates here.
Expected Behavior
user@user:~/source/proj $ sudo /apps/naabu-2.3.4 -host 192.168.1.0/28 -wn -sn -v
__
___ ___ ___ _/ / __ __
/ _ \/ _ \/ _ \/ _ \/ // /
/_//_/\_,_/\_,_/_.__/\_,_/
projectdiscovery.io
[INF] Current naabu version 2.3.4 (outdated)
[WRN] host discovery requires syn scan, automatically switching to syn scan
[INF] Running host discovery scan
[DBG] Received ICMP response from 192.168.1.2
... [redacted for brevity]
[DBG] Received ICMP response from 192.168.1.14
[INF] Found alive host 192.168.1.13 (192.168.1.13)
192.168.1.13
[INF] Found alive host 192.168.1.2 (192.168.1.2)
192.168.1.2
[INF] Found alive host 192.168.1.1 (192.168.1.1)
192.168.1.1
[INF] Found alive host 192.168.1.14 (192.168.1.14)
192.168.1.14
Steps To Reproduce:
Run Naabu 2.3.5 host discovery on a local subnet with kernel 6.12.34+rpt-rpi-v8, others potentially affected.
Additional Information
If we compare strace across host discovery runs from 2.3.4 and 2.3.5, we see mostly a huge difference in system call failures:
user@user:/tmp/difftrace $ grep -F "EPROTONOSUPPORT (Protocol not supported)" /tmp/naabu-2.3.5-strace-host-discovery.txt | wc -l
3462
user@user:/tmp/difftrace $ grep -F "EPROTONOSUPPORT (Protocol not supported)" /tmp/naabu-2.3.4-strace-host-discovery.txt | wc -l
0
...
user@user:/tmp/difftrace $ grep -F "SI_TKILL" /tmp/naabu-2.3.5-strace-host-discovery.txt | wc -l
4334
user@user:/tmp/difftrace $ grep -F "SI_TKILL" /tmp/naabu-2.3.4-strace-host-discovery.txt | wc -l
140
2.3.5
socket(AF_INET6, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_MPTCP) = -1 EPROTONOSUPPORT (Protocol not supported)
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=41333, si_uid=0} ---
...
2.3.4
socket(AF_INET6, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 8
setsockopt(8, SOL_IPV6, IPV6_V6ONLY, [0], 4) = 0
openat(AT_FDCWD, "/proc/sys/net/core/somaxconn", O_RDONLY|O_CLOEXEC) = 9
...
Its unclear to me whether these errors are tied to the total failure in host discovery but indicate something is awry. If there was a CLI change and I'm just ignorant, let me know.