You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only the 80 and 443 are used to scan web server on a host.
It's not good as servers could have multiple web servers (Apache, nginx...) on multiple ports, eg: 8443, 8080 etc ...
So reNgine-ng needs to scan first all ports, detect http server runing on which ports and launch scans (dir fuzz, nuclei ...) on the found ports
Without that we could pass by on juicy target running webserver with default login or many others cases
Alternative solutions
No response
Anything else?
No response
Acknowledgements
This issue is not a duplicate of an existing bug report.
I have chosen an appropriate title.
All requested information has been provided properly.
The text was updated successfully, but these errors were encountered:
Expected feature
Currently only the 80 and 443 are used to scan web server on a host.
It's not good as servers could have multiple web servers (Apache, nginx...) on multiple ports, eg: 8443, 8080 etc ...
So reNgine-ng needs to scan first all ports, detect http server runing on which ports and launch scans (dir fuzz, nuclei ...) on the found ports
Without that we could pass by on juicy target running webserver with default login or many others cases
Alternative solutions
No response
Anything else?
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: