nuclei
nuclei copied to clipboard
projectdiscovery
The program often terminates automatically when the statistical data is less than 100%
When performing a nuclei scan, the program often terminates automatically when the statistical data is less than 100%. I am confused. Does this mean that all scans have been completed? I think it's a bug.
Suspected abnormal scan screenshot:
cmd: nuclei.exe -l targets.txt -me output.md -ts -stats -si 60 -s medium
Could you explain your problem a bit more?
You are saying that Nuclei stops scanning abruptly, even when it should continue, and this tends to happen when there isn't much information being collected about the scan's progress. Right?
Could you explain your problem a bit more?
You are saying that Nuclei stops scanning abruptly, even when it should continue, and this tends to happen when there isn't much information being collected about the scan's progress. Right?
Thank you very much for your reply. I may not have expressed myself clearly enough. I apologize for any inconvenience caused and would like to provide a more detailed description: In theory, I use the - stats and - si parameters to display the progress of nuclei scanning, The scanning process of Nuclei should end when the statistical data reaches 100%, but sometimes it may end automatically before reaching 100%, such as 51%, 57%, 61%, 73%, and so on. If the process is interrupted using Ctrl+C, the resume-xxx.cfg file will be saved to the default path of nuclei. However, the situation where it automatically ends before reaching 100% will not generate the resume-xxx.cfg file and there will be no exceptions or errors. And this situation usually occurs in situations where there are multiple targets and a large number of templates are used to scan each target. (For example, in the picture above, there are over 4000 targets and over 1000 templates, with a total scanning quantity of nearly 20 million. At this time, the statistical data shows that the scanning process ends without warning after reaching over 10 million. I don't know if this means that all scanning processes have been completed.)
some time i have the same problem, I don't know if this is caused by the reasons mentioned in this issue(https://github.com/projectdiscovery/nuclei/issues/3384)。
The stats function is basically not in sync completely according to this issue:
https://github.com/projectdiscovery/nuclei/issues/3384#issuecomment-1453654330
This should be fixed in latest update - https://github.com/projectdiscovery/nuclei/releases/tag/v3.4.3
