Skip to content

Bug in matcher-status option #2693

@ehsandeep

Description

@ehsandeep

Initial feature request - #725; currently, each request returns as a failed result. Instead, the expected behavior is to return failed for the global template matcher condition, like in the case of the matched result but the opposite.

Nuclei version:

dev | master

Current Behavior:

echo https://example.com | nuclei -id CVE-2022-35405 -ms -nts -silent

[CVE-2022-35405] [failed] [http] [critical] https://example.com
[CVE-2022-35405] [failed] [http] [critical] https://example.com
[CVE-2022-35405] [failed] [http] [critical] https://example.com
[CVE-2022-35405] [failed] [http] [critical] https://example.com

Expected Behavior:

echo https://example.com | nuclei -id CVE-2022-35405 -ms -nts -silent

[CVE-2022-35405] [failed] [http] [critical] https://example.com

Steps To Reproduce:

echo https://example.com | nuclei -id CVE-2022-35405 -ms -nts -silent

Anything else:

Related - #2070

Metadata

Metadata

Assignees

Labels

Priority: MediumThis issue may be useful, and needs some attention.Status: CompletedNothing further to be done with this issue. Awaiting to be closed.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions