projectdiscovery / naabu

A fast port scanner written in go with a focus on reliability and simplicity. Designed to be used in combination with other tools for attack surface discovery in bug bounties and pentests
https://projectdiscovery.io
MIT License
4.76k stars 548 forks source link

[FTL] Could not run enumeration: no valid ipv4 or ipv6 targets were found #514

Closed meweez closed 1 year ago

meweez commented 1 year ago

Naabu version:2.1.1

Current Behavior:

when I use this command to scan my network: sudo naabu -p - -host cidr it gives me this error:

  _  _  _ _/ /   __
 / _ \/ _ \/ _ \/ _ \/ // /
/_//_/\_,_/\_,_/_.__/\_,_/ v2.1.1

        projectdiscovery.io

Use with caution. You are responsible for your actions
Developers assume no liability and are not responsible for any misuse or damage.
[INF] Running host discovery scan
[INF] Running SYN scan with CAP_NET_RAW privileges
[FTL] Could not run enumeration: no valid ipv4 or ipv6 targets were found

but if I use naabu version 2.1.0 it doesn't trigger any error.

Expected Behavior:

I want to scan my targeted CIDR.

Steps To Reproduce:

sorry I can not write the target CIDR but its valid and ok with previous version.

Anything else:

No, thanks.

Mzack9999 commented 1 year ago

@meweez This is working for me:

$ go run . -p 22 -host 192.168.1.0/24
...
Use with caution. You are responsible for your actions
Developers assume no liability and are not responsible for any misuse or damage.
[INF] Running host discovery scan
[INF] Running SYN scan with root privileges
[INF] Found 1 ports on host 192.168.1.9 (192.168.1.9)
192.168.1.9:22

Please provide more info about the execution environment. Can you successfully perform the same scan with nmap (with root privileges)?

meweez commented 1 year ago

I could not understand the command yo have used! go run what? and yes, I can scan the range with nmap! Thanks.

Mzack9999 commented 1 year ago

go run . is equivalent to ./naabu if executed within v2/cmd/naabu. Could you provide more info related to the following:

The only thing I can think of is that packets are not routed correctly to the destination, but it's hard to identify the possible reasons without more info. If you use verbose/debug output, are you getting any errors?

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

hosainxade commented 1 year ago

I have this error on latest version!

Screenshot 1402-03-08 at 11 06 16
ehsandeep commented 1 year ago

@hosainxade can you share the output of naabu -hc?

hosainxade commented 1 year ago

@hosainxade can you share the output of naabu -hc?

Sure

Screenshot 1402-03-08 at 16 53 01
mmishalov commented 1 year ago

Have the same issue with both 2.1.1 and 2.1.6.... Is there a fix or workaround available for this?

nickjenkins83 commented 1 year ago

This issue lacks clarity because this exact error occurs if you have http:// or https:// prepended to your domains. If you remove http:// https://; it works just fine