forked from projectdiscovery/nuclei-templates
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.nuclei-ignore
28 lines (24 loc) · 1.29 KB
/
.nuclei-ignore
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
# ==| Nuclei Templates Ignore list |==
# ====================================
#
# This list can be used to define template/s that will be blocked from execution.
# When a folder/directory is listed under this list, the templates within folder can be executed only when running them directly.
# For example, "nuclei -t fuzzing" will not work, "nuclei -t fuzzing/wp-plugin-scan.yaml" will be executed.
#
# Why ignore list? - To ensure nuclei is not getting used to hammer the every web server with templates that are meant to be used for specific use cases.
# and that doesn't mean nuclei won't let you run these templates. if you know what you are doing, feel free to updates this list locally as per your need.
#
# This list also can be used to ignore templates that you wanted to exclude from every scan.
# More details - https://github.com/projectdiscovery/nuclei#using-nuclei-ignore-file-for-template-exclusion
.pre-commit-config.yaml
cves/2013/CVE-2013-2251.yaml
cves/2017/CVE-2017-7529.yaml
cves/2020/CVE-2020-13379.yaml
cves/2020/CVE-2020-16139.yaml
# Fuzzing is excluded to avoid running bruteforce on every server as default.
fuzzing/
# Wordlist directory contains payload to be used with templates.
helpers/
miscellaneous/
# Workflows are excluded from default run to avoid duplicate scans.
workflows/