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
It's problematic because dir_file_fuzz could be launched even if the base endpoint returned 404, and it's the same thing for fetch_url and vulnerability_scan
So we need to rework this part to always send to some tools the base URL, and also correctly set the default URL for root endpoint
Expected Behavior
From the moment we have a subdomain, that have an IP, and give some HTTP response, we must run :
dir_file_fuzz
vulnerability_scan
fetch_url
Steps To Reproduce
Try to launch a scan on a website that have the base URL responding HTTP status code >= 500 or 404
Environment
- reNgine: 2.0.2
- OS: debian
- Python: 3.10
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
According to this issue #7 and some investigation on my side, I think we have a problem with the detection of alive hosts.
I explain
This piece of code is used to check if an endpoint is alive
rengine-ng/web/reNgine/common_func.py
Lines 338 to 340 in 52b4baa
The main problem with this check is that it is used as the base check to launch scan like
rengine-ng/web/reNgine/tasks.py
Lines 1620 to 1628 in 52b4baa
rengine-ng/web/reNgine/tasks.py
Lines 1748 to 1754 in 52b4baa
rengine-ng/web/reNgine/tasks.py
Lines 2305 to 2310 in 52b4baa
rengine-ng/web/reNgine/tasks.py
Lines 2419 to 2424 in 52b4baa
rengine-ng/web/reNgine/tasks.py
Lines 2541 to 2546 in 52b4baa
So the method get_http_urls is mandatory to launch scan of the above type.
The main problem comes from the is_alive method of the Endpoint class in the startScan model
rengine-ng/web/startScan/models.py
Lines 374 to 375 in 52b4baa
As you can see, if, in those conditions :
rengine-ng/web/reNgine/tasks.py
Lines 146 to 152 in 52b4baa
No base url is returned, so no scan is launched.
It's problematic because dir_file_fuzz could be launched even if the base endpoint returned 404, and it's the same thing for fetch_url and vulnerability_scan
So we need to rework this part to always send to some tools the base URL, and also correctly set the default URL for root endpoint
Expected Behavior
From the moment we have a subdomain, that have an IP, and give some HTTP response, we must run :
Steps To Reproduce
Try to launch a scan on a website that have the base URL responding HTTP status code >= 500 or 404
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: