-matcher-status
option to generate result event for errored cases
#4299
Labels
Type: Enhancement
Most issues will probably ask for additions or changes.
Milestone
Please describe your feature request:
When I use nuclei to run my test cases using
matcher-status
option that generates a result event for failed matchers, it doesn't include results when the host got errored out for multiple reasons, which nuclei failed to report.nuclei have a separate option to track errored hosts with error information using
-elog
option, and unfortunately, it can not be mapped directly with the result itself.Describe the use case of this feature:
I'm running nuclei in my CI pipeline, nuclei reported multiple results upon 1st run; as a result of one vulnerability, I've taken down the vulnerable host, upon next nuclei run, nuclei failed to report the same vulnerabilities as it silently failed to run as host is not accessible.
Instead, nuclei can still generate failed match events and populate error information as it does when using with
-elog
option.Here is example run with this support:
1. Test Template
2. Test Run
3. Test Result
Note:
The text was updated successfully, but these errors were encountered: