-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG] -tc is not working as intended with CVE id's #6010
Comments
Note that the value is case-sensitive. $ nuclei -tc "contains(id, 'cve-2021-3110')" -vv
__ _
____ __ _______/ /__ (_)
/ __ \/ / / / ___/ / _ \/ /
/ / / / /_/ / /__/ / __/ /
/_/ /_/\__,_/\___/_/\___/_/ v3.3.8
projectdiscovery.io
[INF] Current nuclei version: v3.3.8 (latest)
[INF] Current nuclei-templates version: v10.1.2 (latest)
[WRN] Scan results upload to cloud is disabled.
[INF] New templates added in latest release: 52
[INF] Templates loaded for current scan: 1
[INF] Executing 1 signed templates from projectdiscovery/nuclei-templates
[CVE-2021-3110] PrestaShop 1.7.7.0 - SQL Injection (@jaimin gondaliya) [critical]
[INF] No results found. Better luck next time! |
nuclei -tc "contains(to_upper(id), 'CVE-202')" -vv |
Template ID is uppercase in template itself, and -id works correctly when set it, why nowhere is stated that -tc need to be always lowercase? |
I see, didn't notice that. Reopening. |
#6016 should fix this issue. |
Yep that PR might fix the issue, thanks |
Is there an existing issue for this?
Current Behavior
Currently when using
nuclei -u https://www.site.com/ -nmhe -tc "contains(id,'CVE-2021-3110')"
returns
[FTL] Could not run nuclei: no templates provided for scan
But when we try to run
nuclei -u https://www.site.com/ -nmhe -id CVE-2021-3110
or
nuclei -u https://www.site.com/ -nmhe -tc "contains(id,'tech-detect')"
Its works as it should be, for some reason -tc parameter is not working with CVE's
Expected Behavior
To execute given CVE template ids
Steps To Reproduce
nuclei -u https://www.site.com/ -nmhe -tc "contains(id,'CVE-2021-3110')
Relevant log output
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: