[Feature Request] Add a flag (e.g., -strict-probe) to stop scanning if internal httpx probe fails (No Fallback) #6648
Closed
sixteen250
started this conversation in
Ideas
Replies: 1 comment
-
|
Tracked at #6652 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When running Nuclei against a target with an open TCP port that is NOT a Web Service (e.g., a "Zombie Port" like a MySQL/Redis port receiving HTTP requests), Nuclei's internal httpx probe correctly identifies that there is no Web Service (Found 0 URL from httpx).
However, Nuclei currently triggers an Auto Fallback mechanism. It ignores the failed probe and proceeds to scan the target using the raw input, assuming it might be a valid HTTP service. In scenarios with large attack surfaces containing many non-HTTP open ports, this causes Nuclei to waste significant time sending thousands of HTTP requests to non-HTTP ports, waiting for timeouts on every request. Even with -mhe set, the scanning continues because TCP connections are successful, but the application layer times out.
I would like a new flag (e.g., -strict-probe or -no-fallback) that changes this behavior. If the internal httpx probe returns 0 URLs (meaning the target is confirmed not to be a Web Service), Nuclei should immediately stop processing that host and not fallback to raw input scanning.
Currently, the only workaround is using a pipeline: echo target:port | httpx | nuclei However, for users who rely on Nuclei's standalone binary or internal logic (e.g., resuming scans, using input files directly), having this logic native to Nuclei would be much more efficient.
Additional context Example of the current inefficient behavior:
Beta Was this translation helpful? Give feedback.
All reactions