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.

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

Skipped website:443 from target list as found unresponsive 30 times after using v3.2.7 #5234

Closed
davidvazquezpf opened this issue May 28, 2024 · 4 comments
Assignees
Labels
Investigation Something to Investigate Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@davidvazquezpf
Copy link

Currently using latest version (3.2.8) and since v.3.2.6 we are experiencing the following issue:
Nuclei is showing: [INF] Skipped ourwebsite:443 from target list as found unresponsive 30 times

We have not changed anything in the current process, it is a scan that is carried out periodically (weekly) for discovering web vulnerabilities in a regular basis after new releases. Running it with version 3.2.6 does not show this problem.

The command we are executing is:
nuclei -u https://www.ourwebsite.com -H User-Agent:scanning_tool --include-tags iot, misc, fuzz, xss, sqli, rce, ssrf, config, cve -fuzz

Any idea about what can be wrong or how to fix it?

Thank you.

@davidvazquezpf davidvazquezpf added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label May 28, 2024
@tarunKoyalwar
Copy link
Member

@davidvazquezpf , we have revamped maxhosterror in #5148 , if you still see max host error and unresponsive host it is most likely a real problem with target

as of now max-host-error is triggered on following errors

var reCheckError = regexp.MustCompile(`(no address found for host|could not resolve host|connection refused|connection reset by peer|could not connect to any address found for host|timeout awaiting response headers)`)
and all of them are critical in nature

for debugging purposes please follow below steps and share what is the actual error returned by server which might be causing this issue

step 1) run nuclei with -elog errors.jsonl flag

step 2) rank / dedupe and count error using

cat errors.jsonl | jq -r '.error' |  sort | uniq -c

@tarunKoyalwar tarunKoyalwar self-assigned this May 28, 2024
@tarunKoyalwar tarunKoyalwar added the Investigation Something to Investigate label May 28, 2024
@davidvazquezpf
Copy link
Author

Thank you very much for the support. Seems to be a problem with the target, we will investigate.

@mattjeff1234
Copy link

hello i have also encountered the same issue .i have uploaded the errors.jsonl file for further investigation .please resolve the issue.
errors.jsonl.txt

@ZerkerEOD
Copy link

I am having the same issue and I have tried it on four or five different sites from our clients. Is there any way to ignore the errors?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Investigation Something to Investigate Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

4 participants