naabu doesn't work well in case of CWAP-WAF

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.7k stars 548 forks source link

naabu doesn't work well in case of CWAP-WAF #341

Closed 0cat-r closed 1 year ago

0cat-r commented 2 years ago

A common situation is that for example, I have 10 ips to scan all ports, but one of them has waf. For example, this time cwap-waf (qianxin security domain) naabu will scan each of his ports, and the speed is full, causing the entire project to be in a few days. can't be done in hours Snipaste_2022-06-01_10-54-46

Snipaste_2022-06-01_10-52-37

My suggestion is to identify waf and handle it like cdn

0cat-r commented 2 years ago

I think a function can be added. If more than a certain number of ports are open, the IP address will be skipped.

Mzack9999 commented 2 years ago

This will be worked on in https://github.com/projectdiscovery/cdncheck/issues/25