Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Targets where host exists but http connection fails #4264

Closed
XTeam-Wing opened this issue Oct 20, 2023 · 2 comments · Fixed by #4265
Closed

Targets where host exists but http connection fails #4264

XTeam-Wing opened this issue Oct 20, 2023 · 2 comments · Fixed by #4265
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.
Milestone
nuclei v3.1.0

Comments

@XTeam-Wing
Copy link
Contributor

Nuclei version:

3.0

Current Behavior:

Continuing to do invalid scanning when http connection fails

Expected Behavior:

When http does not respond multiple times. Exit scanning

Steps To Reproduce:

  1. chose a taget,Targets where host exists but http connection fails
  2. read tcp xxxx->taget ip:5555: read: connection reset by peer
    nuclei -u http://target:5555 -stats -timeout 5
@XTeam-Wing XTeam-Wing added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Oct 20, 2023
@XTeam-Wing XTeam-Wing mentioned this issue Oct 20, 2023
Merged
@Mzack9999
Copy link
Member

@XTeam-Wing nuclei automatically stops testing host:port combinations after the number of failures reaches the host-errors threshold (I think it should be 30). You can lower it, if you want to decrease the error verbosity rate.

@Mzack9999 Mzack9999 added the Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all. label Nov 13, 2023
@dogancanbakir
Copy link
Member

Yes, it is 30. -mhe, -max-host-error int max errors for a host before skipping from scan (default 30)

@ehsandeep ehsandeep linked a pull request Nov 28, 2023 that will close this issue
Fix the bug that nuclei keeps scanning for http connection failures #4265
Merged
@ehsandeep ehsandeep added this to the nuclei v3.1.0 milestone Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.
Projects
None yet
Milestone
nuclei v3.1.0
Development

Successfully merging a pull request may close this issue.

Fix the bug that nuclei keeps scanning for http connection failures Marshal-EASM/nuclei
4 participants
@ehsandeep @Mzack9999 @XTeam-Wing @dogancanbakir