search

projectdiscovery / nuclei

Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
https://docs.projectdiscovery.io/tools/nuclei
MIT License
20.53k stars 2.5k forks source link

nuclei 3.0.0 Could not find template scanning templates via a file #4258

Closed skalvin closed 1 year ago

skalvin commented 1 year ago

i just update my nuclei to the version

[INF] Current nuclei version: v3.0.0 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest)

there's a problem running this command

nuclei -t nuclei-template/

[ERR] Could not find template 'nuclei-templates/': could not find template file: no such path found: nuclei-templates/ [INF] Current nuclei version: v3.0.0 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] Targets loaded for current scan: 43 [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan

before the update it was working fine after the update i got this error

MetzinAround commented 1 year ago

I believe you might need an "s" at the end.

nuclei -u target -t nuclei-templates/

Also, you might need to include home/username/rest/of/path

my command that works is nuclei -t /home/pj/nuclei-templates/ -u TARGET

Also, if you're using -t to run the entire templates folder, you don't need to use -t at all. It will automatically run all the templates in there (except for ones automatically excluded, like fuzzing templates)

ehsandeep commented 1 year ago

@skalvin you don't even need to pass -t option if you wanted to run all / default templates, nuclei as default loads all the public templates, so running nuclei -l url_list.txt or nuclei -u example.com would load / run all the templates, you can use -t option to run specific set of templates.

Moskitoz commented 1 year ago

he's right the last nuclei update, don't run the nuclei scan with -t /template-file/ In the previous version, Nuclei was scanning all the templates in the file with mode -t /template-file/ In the last version, v3.0.0 the -t just run with a specified template path, for example: -t /template-file/xss.yaml

If you run it with -t /template-file/ it will give you the error message "no templates provided for scan"

ehsandeep commented 1 year ago

@Moskitoz I'm unable to reproduce this, what os / system you are using?

nuclei -t ~/nuclei-templates/http/

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.0

        projectdiscovery.io

[INF] Current nuclei version: v3.0.0 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] New templates added in latest release: 1
[INF] Templates loaded for current scan: 6657
[INF] Executing 6658 signed templates from projectdiscovery/nuclei-templates
MetzinAround commented 1 year ago

he's right the last nuclei update, don't run the nuclei scan with -t /template-file/ In the previous version, Nuclei was scanning all the templates in the file with mode -t /template-file/

But if you want to run all the templates, you don't need to specify the path with -t

DroidKali commented 1 year ago

Same issue in the latest version

➜  ~ nuclei -t ./nuclei-templates/http/cves/2023                   
                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

                projectdiscovery.io

[ERR] Could not find template './nuclei-templates/http/cves/2023': could not find template file: no such path found: ./nuclei-templates/http/cves/2023
[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] No results found. Better luck next time!
[FTL] Could not run nuclei: no templates provided for scan
➜  ~ ls ./nuclei-templates/http/cves/2023     
CVE-2023-0099.yaml   CVE-2023-2479.yaml   CVE-2023-33440.yaml
CVE-2023-0126.yaml   CVE-2023-25135.yaml  CVE-2023-3345.yaml
CVE-2023-0236.yaml   CVE-2023-25157.yaml  CVE-2023-33510.yaml
CVE-2023-0261.yaml   CVE-2023-25346.yaml  CVE-2023-33568.yaml
CVE-2023-0297.yaml   CVE-2023-25573.yaml  CVE-2023-33831.yaml
CVE-2023-0448.yaml   CVE-2023-25717.yaml  CVE-2023-34124.yaml
CVE-2023-0514.yaml   CVE-2023-26067.yaml  CVE-2023-34192.yaml
CVE-2023-0527.yaml   CVE-2023-26255.yaml  CVE-2023-34259.yaml
CVE-2023-0552.yaml   CVE-2023-26256.yaml  CVE-2023-34362.yaml
CVE-2023-0562.yaml   CVE-2023-26360.yaml  CVE-2023-34537.yaml
CVE-2023-0563.yaml   CVE-2023-26469.yaml  CVE-2023-34598.yaml
CVE-2023-0630.yaml   CVE-2023-2648.yaml   CVE-2023-34599.yaml
CVE-2023-0669.yaml   CVE-2023-26842.yaml  CVE-2023-3460.yaml
CVE-2023-0942.yaml   CVE-2023-26843.yaml  CVE-2023-34659.yaml
CVE-2023-0948.yaml   CVE-2023-27008.yaml  CVE-2023-3479.yaml
CVE-2023-0968.yaml   CVE-2023-27034.yaml  CVE-2023-34843.yaml
CVE-2023-1020.yaml   CVE-2023-27159.yaml  CVE-2023-34960.yaml
CVE-2023-1080.yaml   CVE-2023-27179.yaml  CVE-2023-35078.yaml
CVE-2023-1177.yaml   CVE-2023-27292.yaml  CVE-2023-35082.yaml
CVE-2023-1362.yaml   CVE-2023-2732.yaml   CVE-2023-35813.yaml
CVE-2023-1434.yaml   CVE-2023-27350.yaml  CVE-2023-35843.yaml
CVE-2023-1454.yaml   CVE-2023-27372.yaml  CVE-2023-35844.yaml
CVE-2023-1496.yaml   CVE-2023-27482.yaml  CVE-2023-35885.yaml
CVE-2023-1546.yaml   CVE-2023-27524.yaml  CVE-2023-36287.yaml
CVE-2023-1671.yaml   CVE-2023-27587.yaml  CVE-2023-36289.yaml
CVE-2023-1698.yaml   CVE-2023-2766.yaml   CVE-2023-36346.yaml
CVE-2023-1730.yaml   CVE-2023-2780.yaml   CVE-2023-36844.yaml
CVE-2023-1835.yaml   CVE-2023-2796.yaml   CVE-2023-36845.yaml
CVE-2023-1890.yaml   CVE-2023-28121.yaml  CVE-2023-36934.yaml
CVE-2023-20073.yaml  CVE-2023-2813.yaml   CVE-2023-3710.yaml
CVE-2023-2023.yaml   CVE-2023-2822.yaml   CVE-2023-37265.yaml
CVE-2023-20864.yaml  CVE-2023-2825.yaml   CVE-2023-37266.yaml
CVE-2023-20887.yaml  CVE-2023-28343.yaml  CVE-2023-37270.yaml
CVE-2023-20888.yaml  CVE-2023-28432.yaml  CVE-2023-37462.yaml
CVE-2023-20889.yaml  CVE-2023-28665.yaml  CVE-2023-37474.yaml
CVE-2023-2122.yaml   CVE-2023-29084.yaml  CVE-2023-37580.yaml
CVE-2023-2130.yaml   CVE-2023-29298.yaml  CVE-2023-37629.yaml
CVE-2023-2178.yaml   CVE-2023-29300.yaml  CVE-2023-3765.yaml
CVE-2023-2224.yaml   CVE-2023-29357.yaml  CVE-2023-38035.yaml
CVE-2023-22432.yaml  CVE-2023-29489.yaml  CVE-2023-38205.yaml
CVE-2023-22463.yaml  CVE-2023-29622.yaml  CVE-2023-3836.yaml
CVE-2023-22478.yaml  CVE-2023-29623.yaml  CVE-2023-38433.yaml
CVE-2023-22480.yaml  CVE-2023-2982.yaml   CVE-2023-38501.yaml
CVE-2023-22515.yaml  CVE-2023-29887.yaml  CVE-2023-38646.yaml
CVE-2023-2252.yaml   CVE-2023-29919.yaml  CVE-2023-39026.yaml
CVE-2023-22620.yaml  CVE-2023-29922.yaml  CVE-2023-39120.yaml
CVE-2023-2272.yaml   CVE-2023-29923.yaml  CVE-2023-39141.yaml
CVE-2023-22897.yaml  CVE-2023-30013.yaml  CVE-2023-39143.yaml
CVE-2023-23161.yaml  CVE-2023-30019.yaml  CVE-2023-39361.yaml
CVE-2023-23333.yaml  CVE-2023-30150.yaml  CVE-2023-3936.yaml
CVE-2023-23488.yaml  CVE-2023-30210.yaml  CVE-2023-39598.yaml
CVE-2023-23489.yaml  CVE-2023-30212.yaml  CVE-2023-39600.yaml
CVE-2023-23491.yaml  CVE-2023-30256.yaml  CVE-2023-39676.yaml
CVE-2023-23492.yaml  CVE-2023-30625.yaml  CVE-2023-39677.yaml
CVE-2023-2356.yaml   CVE-2023-30777.yaml  CVE-2023-41642.yaml
CVE-2023-23752.yaml  CVE-2023-30943.yaml  CVE-2023-4173.yaml
CVE-2023-24044.yaml  CVE-2023-31059.yaml  CVE-2023-4174.yaml
CVE-2023-24243.yaml  CVE-2023-31465.yaml  CVE-2023-41892.yaml
CVE-2023-24278.yaml  CVE-2023-31548.yaml  CVE-2023-42442.yaml
CVE-2023-24322.yaml  CVE-2023-32117.yaml  CVE-2023-42793.yaml
CVE-2023-24367.yaml  CVE-2023-32235.yaml  CVE-2023-43261.yaml
CVE-2023-24488.yaml  CVE-2023-32243.yaml  CVE-2023-4451.yaml
CVE-2023-24489.yaml  CVE-2023-32315.yaml  CVE-2023-4568.yaml
CVE-2023-24657.yaml  CVE-2023-32563.yaml  CVE-2023-4634.yaml
CVE-2023-24733.yaml  CVE-2023-33338.yaml  CVE-2023-4714.yaml
CVE-2023-24735.yaml  CVE-2023-33405.yaml  CVE-2023-5074.yaml
CVE-2023-24737.yaml  CVE-2023-33439.yaml
➜  ~
DroidKali commented 1 year ago

Same issue in the latest version

➜  ~ nuclei -t ./nuclei-templates/http/cves/2023                   
                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

                projectdiscovery.io

[ERR] Could not find template './nuclei-templates/http/cves/2023': could not find template file: no such path found: ./nuclei-templates/http/cves/2023
[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] No results found. Better luck next time!
[FTL] Could not run nuclei: no templates provided for scan
➜  ~ ls ./nuclei-templates/http/cves/2023     
CVE-2023-0099.yaml   CVE-2023-2479.yaml   CVE-2023-33440.yaml
CVE-2023-0126.yaml   CVE-2023-25135.yaml  CVE-2023-3345.yaml
CVE-2023-0236.yaml   CVE-2023-25157.yaml  CVE-2023-33510.yaml
CVE-2023-0261.yaml   CVE-2023-25346.yaml  CVE-2023-33568.yaml
CVE-2023-0297.yaml   CVE-2023-25573.yaml  CVE-2023-33831.yaml
CVE-2023-0448.yaml   CVE-2023-25717.yaml  CVE-2023-34124.yaml
CVE-2023-0514.yaml   CVE-2023-26067.yaml  CVE-2023-34192.yaml
CVE-2023-0527.yaml   CVE-2023-26255.yaml  CVE-2023-34259.yaml
CVE-2023-0552.yaml   CVE-2023-26256.yaml  CVE-2023-34362.yaml
CVE-2023-0562.yaml   CVE-2023-26360.yaml  CVE-2023-34537.yaml
CVE-2023-0563.yaml   CVE-2023-26469.yaml  CVE-2023-34598.yaml
CVE-2023-0630.yaml   CVE-2023-2648.yaml   CVE-2023-34599.yaml
CVE-2023-0669.yaml   CVE-2023-26842.yaml  CVE-2023-3460.yaml
CVE-2023-0942.yaml   CVE-2023-26843.yaml  CVE-2023-34659.yaml
CVE-2023-0948.yaml   CVE-2023-27008.yaml  CVE-2023-3479.yaml
CVE-2023-0968.yaml   CVE-2023-27034.yaml  CVE-2023-34843.yaml
CVE-2023-1020.yaml   CVE-2023-27159.yaml  CVE-2023-34960.yaml
CVE-2023-1080.yaml   CVE-2023-27179.yaml  CVE-2023-35078.yaml
CVE-2023-1177.yaml   CVE-2023-27292.yaml  CVE-2023-35082.yaml
CVE-2023-1362.yaml   CVE-2023-2732.yaml   CVE-2023-35813.yaml
CVE-2023-1434.yaml   CVE-2023-27350.yaml  CVE-2023-35843.yaml
CVE-2023-1454.yaml   CVE-2023-27372.yaml  CVE-2023-35844.yaml
CVE-2023-1496.yaml   CVE-2023-27482.yaml  CVE-2023-35885.yaml
CVE-2023-1546.yaml   CVE-2023-27524.yaml  CVE-2023-36287.yaml
CVE-2023-1671.yaml   CVE-2023-27587.yaml  CVE-2023-36289.yaml
CVE-2023-1698.yaml   CVE-2023-2766.yaml   CVE-2023-36346.yaml
CVE-2023-1730.yaml   CVE-2023-2780.yaml   CVE-2023-36844.yaml
CVE-2023-1835.yaml   CVE-2023-2796.yaml   CVE-2023-36845.yaml
CVE-2023-1890.yaml   CVE-2023-28121.yaml  CVE-2023-36934.yaml
CVE-2023-20073.yaml  CVE-2023-2813.yaml   CVE-2023-3710.yaml
CVE-2023-2023.yaml   CVE-2023-2822.yaml   CVE-2023-37265.yaml
CVE-2023-20864.yaml  CVE-2023-2825.yaml   CVE-2023-37266.yaml
CVE-2023-20887.yaml  CVE-2023-28343.yaml  CVE-2023-37270.yaml
CVE-2023-20888.yaml  CVE-2023-28432.yaml  CVE-2023-37462.yaml
CVE-2023-20889.yaml  CVE-2023-28665.yaml  CVE-2023-37474.yaml
CVE-2023-2122.yaml   CVE-2023-29084.yaml  CVE-2023-37580.yaml
CVE-2023-2130.yaml   CVE-2023-29298.yaml  CVE-2023-37629.yaml
CVE-2023-2178.yaml   CVE-2023-29300.yaml  CVE-2023-3765.yaml
CVE-2023-2224.yaml   CVE-2023-29357.yaml  CVE-2023-38035.yaml
CVE-2023-22432.yaml  CVE-2023-29489.yaml  CVE-2023-38205.yaml
CVE-2023-22463.yaml  CVE-2023-29622.yaml  CVE-2023-3836.yaml
CVE-2023-22478.yaml  CVE-2023-29623.yaml  CVE-2023-38433.yaml
CVE-2023-22480.yaml  CVE-2023-2982.yaml   CVE-2023-38501.yaml
CVE-2023-22515.yaml  CVE-2023-29887.yaml  CVE-2023-38646.yaml
CVE-2023-2252.yaml   CVE-2023-29919.yaml  CVE-2023-39026.yaml
CVE-2023-22620.yaml  CVE-2023-29922.yaml  CVE-2023-39120.yaml
CVE-2023-2272.yaml   CVE-2023-29923.yaml  CVE-2023-39141.yaml
CVE-2023-22897.yaml  CVE-2023-30013.yaml  CVE-2023-39143.yaml
CVE-2023-23161.yaml  CVE-2023-30019.yaml  CVE-2023-39361.yaml
CVE-2023-23333.yaml  CVE-2023-30150.yaml  CVE-2023-3936.yaml
CVE-2023-23488.yaml  CVE-2023-30210.yaml  CVE-2023-39598.yaml
CVE-2023-23489.yaml  CVE-2023-30212.yaml  CVE-2023-39600.yaml
CVE-2023-23491.yaml  CVE-2023-30256.yaml  CVE-2023-39676.yaml
CVE-2023-23492.yaml  CVE-2023-30625.yaml  CVE-2023-39677.yaml
CVE-2023-2356.yaml   CVE-2023-30777.yaml  CVE-2023-41642.yaml
CVE-2023-23752.yaml  CVE-2023-30943.yaml  CVE-2023-4173.yaml
CVE-2023-24044.yaml  CVE-2023-31059.yaml  CVE-2023-4174.yaml
CVE-2023-24243.yaml  CVE-2023-31465.yaml  CVE-2023-41892.yaml
CVE-2023-24278.yaml  CVE-2023-31548.yaml  CVE-2023-42442.yaml
CVE-2023-24322.yaml  CVE-2023-32117.yaml  CVE-2023-42793.yaml
CVE-2023-24367.yaml  CVE-2023-32235.yaml  CVE-2023-43261.yaml
CVE-2023-24488.yaml  CVE-2023-32243.yaml  CVE-2023-4451.yaml
CVE-2023-24489.yaml  CVE-2023-32315.yaml  CVE-2023-4568.yaml
CVE-2023-24657.yaml  CVE-2023-32563.yaml  CVE-2023-4634.yaml
CVE-2023-24733.yaml  CVE-2023-33338.yaml  CVE-2023-4714.yaml
CVE-2023-24735.yaml  CVE-2023-33405.yaml  CVE-2023-5074.yaml
CVE-2023-24737.yaml  CVE-2023-33439.yaml
➜  ~

It should be an absolute path problem. Use an absolute path to specify the templates directory instead of a relative path.

➜  ~ nuclei -t ./nuclei-templates/http/cves/2023                                        __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

                projectdiscovery.io

[ERR] Could not find template './nuclei-templates/http/cves/2023': could not find template file: no such path found: ./nuclei-templates/http/cves/2023
[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] No results found. Better luck next time!
[FTL] Could not run nuclei: no templates provided for scan
➜  ~ nuclei -t /root/nuclei-templates/http/cves/2023               
                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

                projectdiscovery.io

[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] New templates added in latest release: 1
[INF] Templates loaded for current scan: 251
[INF] Executing 251 signed templates from projectdiscovery/nuclei-templates
[INF] No results found. Better luck next time!
➜  ~ ls ./nuclei-templates/http/cves/2023
CVE-2023-0099.yaml   CVE-2023-26067.yaml  CVE-2023-34755.yaml
CVE-2023-0126.yaml   CVE-2023-26255.yaml  CVE-2023-34756.yaml
CVE-2023-0236.yaml   CVE-2023-26256.yaml  CVE-2023-3479.yaml
CVE-2023-0261.yaml   CVE-2023-26360.yaml  CVE-2023-34843.yaml
CVE-2023-0297.yaml   CVE-2023-26469.yaml  CVE-2023-34960.yaml
CVE-2023-0334.yaml   CVE-2023-2648.yaml   CVE-2023-35078.yaml
CVE-2023-0448.yaml   CVE-2023-26842.yaml  CVE-2023-35082.yaml
CVE-2023-0514.yaml   CVE-2023-26843.yaml  CVE-2023-35813.yaml
CVE-2023-0527.yaml   CVE-2023-27008.yaml  CVE-2023-35843.yaml
CVE-2023-0552.yaml   CVE-2023-27034.yaml  CVE-2023-35844.yaml
CVE-2023-0562.yaml   CVE-2023-27159.yaml  CVE-2023-35885.yaml
CVE-2023-0563.yaml   CVE-2023-27179.yaml  CVE-2023-36287.yaml
CVE-2023-0600.yaml   CVE-2023-27292.yaml  CVE-2023-36289.yaml
CVE-2023-0602.yaml   CVE-2023-2732.yaml   CVE-2023-36306.yaml
CVE-2023-0630.yaml   CVE-2023-27350.yaml  CVE-2023-36346.yaml
CVE-2023-0669.yaml   CVE-2023-27372.yaml  CVE-2023-36844.yaml
CVE-2023-0777.yaml   CVE-2023-27482.yaml  CVE-2023-36845.yaml
CVE-2023-0900.yaml   CVE-2023-27524.yaml  CVE-2023-36934.yaml
CVE-2023-0942.yaml   CVE-2023-27587.yaml  CVE-2023-3710.yaml
CVE-2023-0947.yaml   CVE-2023-2766.yaml   CVE-2023-37265.yaml
CVE-2023-0948.yaml   CVE-2023-2779.yaml   CVE-2023-37266.yaml
CVE-2023-0968.yaml   CVE-2023-2780.yaml   CVE-2023-37270.yaml
CVE-2023-1020.yaml   CVE-2023-27922.yaml  CVE-2023-37462.yaml
CVE-2023-1080.yaml   CVE-2023-2796.yaml   CVE-2023-37474.yaml
CVE-2023-1177.yaml   CVE-2023-28121.yaml  CVE-2023-37580.yaml
CVE-2023-1263.yaml   CVE-2023-2813.yaml   CVE-2023-37629.yaml
CVE-2023-1362.yaml   CVE-2023-2822.yaml   CVE-2023-3765.yaml
CVE-2023-1408.yaml   CVE-2023-2825.yaml   CVE-2023-37728.yaml
CVE-2023-1434.yaml   CVE-2023-28343.yaml  CVE-2023-37979.yaml
CVE-2023-1454.yaml   CVE-2023-28432.yaml  CVE-2023-38035.yaml
CVE-2023-1496.yaml   CVE-2023-28665.yaml  CVE-2023-38205.yaml
CVE-2023-1546.yaml   CVE-2023-29084.yaml  CVE-2023-3836.yaml
CVE-2023-1671.yaml   CVE-2023-29298.yaml  CVE-2023-38433.yaml
CVE-2023-1698.yaml   CVE-2023-29300.yaml  CVE-2023-3843.yaml
CVE-2023-1730.yaml   CVE-2023-29357.yaml  CVE-2023-3844.yaml
CVE-2023-1780.yaml   CVE-2023-29439.yaml  CVE-2023-3845.yaml
CVE-2023-1835.yaml   CVE-2023-29489.yaml  CVE-2023-3846.yaml
CVE-2023-1880.yaml   CVE-2023-29622.yaml  CVE-2023-3847.yaml
CVE-2023-1890.yaml   CVE-2023-29623.yaml  CVE-2023-3848.yaml
CVE-2023-20073.yaml  CVE-2023-2982.yaml   CVE-2023-3849.yaml
CVE-2023-2009.yaml   CVE-2023-29887.yaml  CVE-2023-38501.yaml
CVE-2023-2023.yaml   CVE-2023-29919.yaml  CVE-2023-38646.yaml
CVE-2023-20864.yaml  CVE-2023-29922.yaml  CVE-2023-39026.yaml
CVE-2023-20887.yaml  CVE-2023-29923.yaml  CVE-2023-39108.yaml
CVE-2023-20888.yaml  CVE-2023-30013.yaml  CVE-2023-39109.yaml
CVE-2023-20889.yaml  CVE-2023-30019.yaml  CVE-2023-39110.yaml
CVE-2023-2122.yaml   CVE-2023-30150.yaml  CVE-2023-39120.yaml
CVE-2023-2130.yaml   CVE-2023-30210.yaml  CVE-2023-39141.yaml
CVE-2023-2178.yaml   CVE-2023-30212.yaml  CVE-2023-39143.yaml
CVE-2023-2224.yaml   CVE-2023-30256.yaml  CVE-2023-39361.yaml
CVE-2023-22432.yaml  CVE-2023-30625.yaml  CVE-2023-3936.yaml
CVE-2023-22463.yaml  CVE-2023-30777.yaml  CVE-2023-39598.yaml
CVE-2023-22478.yaml  CVE-2023-30868.yaml  CVE-2023-39600.yaml
CVE-2023-22480.yaml  CVE-2023-30943.yaml  CVE-2023-39676.yaml
CVE-2023-22515.yaml  CVE-2023-31059.yaml  CVE-2023-39677.yaml
CVE-2023-2252.yaml   CVE-2023-31465.yaml  CVE-2023-39700.yaml
CVE-2023-22620.yaml  CVE-2023-31548.yaml  CVE-2023-40208.yaml
CVE-2023-2272.yaml   CVE-2023-32117.yaml  CVE-2023-40779.yaml
CVE-2023-22897.yaml  CVE-2023-3219.yaml   CVE-2023-4110.yaml
CVE-2023-23161.yaml  CVE-2023-32235.yaml  CVE-2023-4111.yaml
CVE-2023-23333.yaml  CVE-2023-32243.yaml  CVE-2023-4112.yaml
CVE-2023-23488.yaml  CVE-2023-32315.yaml  CVE-2023-4113.yaml
CVE-2023-23489.yaml  CVE-2023-32563.yaml  CVE-2023-4114.yaml
CVE-2023-23491.yaml  CVE-2023-33338.yaml  CVE-2023-4115.yaml
CVE-2023-23492.yaml  CVE-2023-33405.yaml  CVE-2023-4116.yaml
CVE-2023-2356.yaml   CVE-2023-33439.yaml  CVE-2023-4148.yaml
CVE-2023-23752.yaml  CVE-2023-33440.yaml  CVE-2023-41538.yaml
CVE-2023-24044.yaml  CVE-2023-3345.yaml   CVE-2023-41642.yaml
CVE-2023-24243.yaml  CVE-2023-33510.yaml  CVE-2023-4168.yaml
CVE-2023-24278.yaml  CVE-2023-33568.yaml  CVE-2023-4173.yaml
CVE-2023-24322.yaml  CVE-2023-33584.yaml  CVE-2023-4174.yaml
CVE-2023-24367.yaml  CVE-2023-33831.yaml  CVE-2023-41892.yaml
CVE-2023-24488.yaml  CVE-2023-34124.yaml  CVE-2023-42442.yaml
CVE-2023-24489.yaml  CVE-2023-34192.yaml  CVE-2023-42793.yaml
CVE-2023-24657.yaml  CVE-2023-34259.yaml  CVE-2023-43261.yaml
CVE-2023-24733.yaml  CVE-2023-34362.yaml  CVE-2023-4451.yaml
CVE-2023-24735.yaml  CVE-2023-34537.yaml  CVE-2023-4547.yaml
CVE-2023-24737.yaml  CVE-2023-34598.yaml  CVE-2023-4568.yaml
CVE-2023-2479.yaml   CVE-2023-34599.yaml  CVE-2023-4634.yaml
CVE-2023-25135.yaml  CVE-2023-3460.yaml   CVE-2023-4714.yaml
➜  ~
Moafsptwenr commented 1 year ago

unsubscribe

在 2023-10-21 16:23:20，"DroidKali" @.***> 写道：

Same issue in the latest version

➜ ~ nuclei -t ./nuclei-templates/http/cves/2023

__ ___/ / (_) / \/ / / / / / \/ / / / / / // / // / / / // //_,/\/_/__// v3.0.1

            projectdiscovery.io

[ERR] Could not find template './nuclei-templates/http/cves/2023': could not find template file: no such path found: ./nuclei-templates/http/cves/2023 [INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan ➜ ~ ls ./nuclei-templates/http/cves/2023
CVE-2023-0099.yaml CVE-2023-2479.yaml CVE-2023-33440.yaml CVE-2023-0126.yaml CVE-2023-25135.yaml CVE-2023-3345.yaml CVE-2023-0236.yaml CVE-2023-25157.yaml CVE-2023-33510.yaml CVE-2023-0261.yaml CVE-2023-25346.yaml CVE-2023-33568.yaml CVE-2023-0297.yaml CVE-2023-25573.yaml CVE-2023-33831.yaml CVE-2023-0448.yaml CVE-2023-25717.yaml CVE-2023-34124.yaml CVE-2023-0514.yaml CVE-2023-26067.yaml CVE-2023-34192.yaml CVE-2023-0527.yaml CVE-2023-26255.yaml CVE-2023-34259.yaml CVE-2023-0552.yaml CVE-2023-26256.yaml CVE-2023-34362.yaml CVE-2023-0562.yaml CVE-2023-26360.yaml CVE-2023-34537.yaml CVE-2023-0563.yaml CVE-2023-26469.yaml CVE-2023-34598.yaml CVE-2023-0630.yaml CVE-2023-2648.yaml CVE-2023-34599.yaml CVE-2023-0669.yaml CVE-2023-26842.yaml CVE-2023-3460.yaml CVE-2023-0942.yaml CVE-2023-26843.yaml CVE-2023-34659.yaml CVE-2023-0948.yaml CVE-2023-27008.yaml CVE-2023-3479.yaml CVE-2023-0968.yaml CVE-2023-27034.yaml CVE-2023-34843.yaml CVE-2023-1020.yaml CVE-2023-27159.yaml CVE-2023-34960.yaml CVE-2023-1080.yaml CVE-2023-27179.yaml CVE-2023-35078.yaml CVE-2023-1177.yaml CVE-2023-27292.yaml CVE-2023-35082.yaml CVE-2023-1362.yaml CVE-2023-2732.yaml CVE-2023-35813.yaml CVE-2023-1434.yaml CVE-2023-27350.yaml CVE-2023-35843.yaml CVE-2023-1454.yaml CVE-2023-27372.yaml CVE-2023-35844.yaml CVE-2023-1496.yaml CVE-2023-27482.yaml CVE-2023-35885.yaml CVE-2023-1546.yaml CVE-2023-27524.yaml CVE-2023-36287.yaml CVE-2023-1671.yaml CVE-2023-27587.yaml CVE-2023-36289.yaml CVE-2023-1698.yaml CVE-2023-2766.yaml CVE-2023-36346.yaml CVE-2023-1730.yaml CVE-2023-2780.yaml CVE-2023-36844.yaml CVE-2023-1835.yaml CVE-2023-2796.yaml CVE-2023-36845.yaml CVE-2023-1890.yaml CVE-2023-28121.yaml CVE-2023-36934.yaml CVE-2023-20073.yaml CVE-2023-2813.yaml CVE-2023-3710.yaml CVE-2023-2023.yaml CVE-2023-2822.yaml CVE-2023-37265.yaml CVE-2023-20864.yaml CVE-2023-2825.yaml CVE-2023-37266.yaml CVE-2023-20887.yaml CVE-2023-28343.yaml CVE-2023-37270.yaml CVE-2023-20888.yaml CVE-2023-28432.yaml CVE-2023-37462.yaml CVE-2023-20889.yaml CVE-2023-28665.yaml CVE-2023-37474.yaml CVE-2023-2122.yaml CVE-2023-29084.yaml CVE-2023-37580.yaml CVE-2023-2130.yaml CVE-2023-29298.yaml CVE-2023-37629.yaml CVE-2023-2178.yaml CVE-2023-29300.yaml CVE-2023-3765.yaml CVE-2023-2224.yaml CVE-2023-29357.yaml CVE-2023-38035.yaml CVE-2023-22432.yaml CVE-2023-29489.yaml CVE-2023-38205.yaml CVE-2023-22463.yaml CVE-2023-29622.yaml CVE-2023-3836.yaml CVE-2023-22478.yaml CVE-2023-29623.yaml CVE-2023-38433.yaml CVE-2023-22480.yaml CVE-2023-2982.yaml CVE-2023-38501.yaml CVE-2023-22515.yaml CVE-2023-29887.yaml CVE-2023-38646.yaml CVE-2023-2252.yaml CVE-2023-29919.yaml CVE-2023-39026.yaml CVE-2023-22620.yaml CVE-2023-29922.yaml CVE-2023-39120.yaml CVE-2023-2272.yaml CVE-2023-29923.yaml CVE-2023-39141.yaml CVE-2023-22897.yaml CVE-2023-30013.yaml CVE-2023-39143.yaml CVE-2023-23161.yaml CVE-2023-30019.yaml CVE-2023-39361.yaml CVE-2023-23333.yaml CVE-2023-30150.yaml CVE-2023-3936.yaml CVE-2023-23488.yaml CVE-2023-30210.yaml CVE-2023-39598.yaml CVE-2023-23489.yaml CVE-2023-30212.yaml CVE-2023-39600.yaml CVE-2023-23491.yaml CVE-2023-30256.yaml CVE-2023-39676.yaml CVE-2023-23492.yaml CVE-2023-30625.yaml CVE-2023-39677.yaml CVE-2023-2356.yaml CVE-2023-30777.yaml CVE-2023-41642.yaml CVE-2023-23752.yaml CVE-2023-30943.yaml CVE-2023-4173.yaml CVE-2023-24044.yaml CVE-2023-31059.yaml CVE-2023-4174.yaml CVE-2023-24243.yaml CVE-2023-31465.yaml CVE-2023-41892.yaml CVE-2023-24278.yaml CVE-2023-31548.yaml CVE-2023-42442.yaml CVE-2023-24322.yaml CVE-2023-32117.yaml CVE-2023-42793.yaml CVE-2023-24367.yaml CVE-2023-32235.yaml CVE-2023-43261.yaml CVE-2023-24488.yaml CVE-2023-32243.yaml CVE-2023-4451.yaml CVE-2023-24489.yaml CVE-2023-32315.yaml CVE-2023-4568.yaml CVE-2023-24657.yaml CVE-2023-32563.yaml CVE-2023-4634.yaml CVE-2023-24733.yaml CVE-2023-33338.yaml CVE-2023-4714.yaml CVE-2023-24735.yaml CVE-2023-33405.yaml CVE-2023-5074.yaml CVE-2023-24737.yaml CVE-2023-33439.yaml ➜ ~

It should be an absolute path problem. Use an absolute path to specify the templates directory instead of a relative path.

➜ ~ nuclei -t ./nuclei-templates/http/cves/2023 _ __ _____/ / (_) / _ \/ / / / / / \/ / / / / / // / // / / / // //_,/_//\/_/ v3.0.1

            projectdiscovery.io

[ERR] Could not find template './nuclei-templates/http/cves/2023': could not find template file: no such path found: ./nuclei-templates/http/cves/2023 [INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan ➜ ~ nuclei -t /root/nuclei-templates/http/cves/2023

__ ___/ / (_) / \/ / / / / / \/ / / / / / // / // / / / // //_,/\/_/__// v3.0.1

            projectdiscovery.io

[INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] New templates added in latest release: 1 [INF] Templates loaded for current scan: 251 [INF] Executing 251 signed templates from projectdiscovery/nuclei-templates [INF] No results found. Better luck next time! ➜ ~ ls ./nuclei-templates/http/cves/2023 CVE-2023-0099.yaml CVE-2023-26067.yaml CVE-2023-34755.yaml CVE-2023-0126.yaml CVE-2023-26255.yaml CVE-2023-34756.yaml CVE-2023-0236.yaml CVE-2023-26256.yaml CVE-2023-3479.yaml CVE-2023-0261.yaml CVE-2023-26360.yaml CVE-2023-34843.yaml CVE-2023-0297.yaml CVE-2023-26469.yaml CVE-2023-34960.yaml CVE-2023-0334.yaml CVE-2023-2648.yaml CVE-2023-35078.yaml CVE-2023-0448.yaml CVE-2023-26842.yaml CVE-2023-35082.yaml CVE-2023-0514.yaml CVE-2023-26843.yaml CVE-2023-35813.yaml CVE-2023-0527.yaml CVE-2023-27008.yaml CVE-2023-35843.yaml CVE-2023-0552.yaml CVE-2023-27034.yaml CVE-2023-35844.yaml CVE-2023-0562.yaml CVE-2023-27159.yaml CVE-2023-35885.yaml CVE-2023-0563.yaml CVE-2023-27179.yaml CVE-2023-36287.yaml CVE-2023-0600.yaml CVE-2023-27292.yaml CVE-2023-36289.yaml CVE-2023-0602.yaml CVE-2023-2732.yaml CVE-2023-36306.yaml CVE-2023-0630.yaml CVE-2023-27350.yaml CVE-2023-36346.yaml CVE-2023-0669.yaml CVE-2023-27372.yaml CVE-2023-36844.yaml CVE-2023-0777.yaml CVE-2023-27482.yaml CVE-2023-36845.yaml CVE-2023-0900.yaml CVE-2023-27524.yaml CVE-2023-36934.yaml CVE-2023-0942.yaml CVE-2023-27587.yaml CVE-2023-3710.yaml CVE-2023-0947.yaml CVE-2023-2766.yaml CVE-2023-37265.yaml CVE-2023-0948.yaml CVE-2023-2779.yaml CVE-2023-37266.yaml CVE-2023-0968.yaml CVE-2023-2780.yaml CVE-2023-37270.yaml CVE-2023-1020.yaml CVE-2023-27922.yaml CVE-2023-37462.yaml CVE-2023-1080.yaml CVE-2023-2796.yaml CVE-2023-37474.yaml CVE-2023-1177.yaml CVE-2023-28121.yaml CVE-2023-37580.yaml CVE-2023-1263.yaml CVE-2023-2813.yaml CVE-2023-37629.yaml CVE-2023-1362.yaml CVE-2023-2822.yaml CVE-2023-3765.yaml CVE-2023-1408.yaml CVE-2023-2825.yaml CVE-2023-37728.yaml CVE-2023-1434.yaml CVE-2023-28343.yaml CVE-2023-37979.yaml CVE-2023-1454.yaml CVE-2023-28432.yaml CVE-2023-38035.yaml CVE-2023-1496.yaml CVE-2023-28665.yaml CVE-2023-38205.yaml CVE-2023-1546.yaml CVE-2023-29084.yaml CVE-2023-3836.yaml CVE-2023-1671.yaml CVE-2023-29298.yaml CVE-2023-38433.yaml CVE-2023-1698.yaml CVE-2023-29300.yaml CVE-2023-3843.yaml CVE-2023-1730.yaml CVE-2023-29357.yaml CVE-2023-3844.yaml CVE-2023-1780.yaml CVE-2023-29439.yaml CVE-2023-3845.yaml CVE-2023-1835.yaml CVE-2023-29489.yaml CVE-2023-3846.yaml CVE-2023-1880.yaml CVE-2023-29622.yaml CVE-2023-3847.yaml CVE-2023-1890.yaml CVE-2023-29623.yaml CVE-2023-3848.yaml CVE-2023-20073.yaml CVE-2023-2982.yaml CVE-2023-3849.yaml CVE-2023-2009.yaml CVE-2023-29887.yaml CVE-2023-38501.yaml CVE-2023-2023.yaml CVE-2023-29919.yaml CVE-2023-38646.yaml CVE-2023-20864.yaml CVE-2023-29922.yaml CVE-2023-39026.yaml CVE-2023-20887.yaml CVE-2023-29923.yaml CVE-2023-39108.yaml CVE-2023-20888.yaml CVE-2023-30013.yaml CVE-2023-39109.yaml CVE-2023-20889.yaml CVE-2023-30019.yaml CVE-2023-39110.yaml CVE-2023-2122.yaml CVE-2023-30150.yaml CVE-2023-39120.yaml CVE-2023-2130.yaml CVE-2023-30210.yaml CVE-2023-39141.yaml CVE-2023-2178.yaml CVE-2023-30212.yaml CVE-2023-39143.yaml CVE-2023-2224.yaml CVE-2023-30256.yaml CVE-2023-39361.yaml CVE-2023-22432.yaml CVE-2023-30625.yaml CVE-2023-3936.yaml CVE-2023-22463.yaml CVE-2023-30777.yaml CVE-2023-39598.yaml CVE-2023-22478.yaml CVE-2023-30868.yaml CVE-2023-39600.yaml CVE-2023-22480.yaml CVE-2023-30943.yaml CVE-2023-39676.yaml CVE-2023-22515.yaml CVE-2023-31059.yaml CVE-2023-39677.yaml CVE-2023-2252.yaml CVE-2023-31465.yaml CVE-2023-39700.yaml CVE-2023-22620.yaml CVE-2023-31548.yaml CVE-2023-40208.yaml CVE-2023-2272.yaml CVE-2023-32117.yaml CVE-2023-40779.yaml CVE-2023-22897.yaml CVE-2023-3219.yaml CVE-2023-4110.yaml CVE-2023-23161.yaml CVE-2023-32235.yaml CVE-2023-4111.yaml CVE-2023-23333.yaml CVE-2023-32243.yaml CVE-2023-4112.yaml CVE-2023-23488.yaml CVE-2023-32315.yaml CVE-2023-4113.yaml CVE-2023-23489.yaml CVE-2023-32563.yaml CVE-2023-4114.yaml CVE-2023-23491.yaml CVE-2023-33338.yaml CVE-2023-4115.yaml CVE-2023-23492.yaml CVE-2023-33405.yaml CVE-2023-4116.yaml CVE-2023-2356.yaml CVE-2023-33439.yaml CVE-2023-4148.yaml CVE-2023-23752.yaml CVE-2023-33440.yaml CVE-2023-41538.yaml CVE-2023-24044.yaml CVE-2023-3345.yaml CVE-2023-41642.yaml CVE-2023-24243.yaml CVE-2023-33510.yaml CVE-2023-4168.yaml CVE-2023-24278.yaml CVE-2023-33568.yaml CVE-2023-4173.yaml CVE-2023-24322.yaml CVE-2023-33584.yaml CVE-2023-4174.yaml CVE-2023-24367.yaml CVE-2023-33831.yaml CVE-2023-41892.yaml CVE-2023-24488.yaml CVE-2023-34124.yaml CVE-2023-42442.yaml CVE-2023-24489.yaml CVE-2023-34192.yaml CVE-2023-42793.yaml CVE-2023-24657.yaml CVE-2023-34259.yaml CVE-2023-43261.yaml CVE-2023-24733.yaml CVE-2023-34362.yaml CVE-2023-4451.yaml CVE-2023-24735.yaml CVE-2023-34537.yaml CVE-2023-4547.yaml CVE-2023-24737.yaml CVE-2023-34598.yaml CVE-2023-4568.yaml CVE-2023-2479.yaml CVE-2023-34599.yaml CVE-2023-4634.yaml CVE-2023-25135.yaml CVE-2023-3460.yaml CVE-2023-4714.yaml ➜ ~

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

skalvin commented 1 year ago

he's right the last nuclei update, don't run the nuclei scan with -t /template-file/ In the previous version, Nuclei was scanning all the templates in the file with mode -t /template-file/

But if you want to run all the templates, you don't need to specify the path with -t

Hello, thanks for the reply.

before the update 3.0.0 and 3.0.1 On the same system and with the same setup, it was working fine. It's not complicated.

The command I'm using is so simple.

cat results.txt | uro | nuclei -t fuzz/

[ERR] Could not find template 'fuzz/': could not find template file: no such path found: fuzz/ [INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] Targets loaded for current scan: 2458 [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan

Before the latest update, it was running the scan normally.

Note: fuzz/ is the file where I put some specified YAML templates to scan.

skalvin commented 1 year ago

@Moskitoz I'm unable to reproduce this, what os / system you are using?

nuclei -t ~/nuclei-templates/http/

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.0

      projectdiscovery.io

[INF] Current nuclei version: v3.0.0 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] New templates added in latest release: 1
[INF] Templates loaded for current scan: 6657
[INF] Executing 6658 signed templates from projectdiscovery/nuclei-templates

i run it on Google-Cloud Shell it was working fine without any ERROR before the latest update (3.0.0/3.0.1)

DroidKali commented 1 year ago

he's right the last nuclei update, don't run the nuclei scan with -t /template-file/ In the previous version, Nuclei was scanning all the templates in the file with mode -t /template-file/

But if you want to run all the templates, you don't need to specify the path with -t

Hello, thanks for the reply.

before the update 3.0.0 and 3.0.1 On the same system and with the same setup, it was working fine. It's not complicated.

The command I'm using is so simple.

cat results.txt | uro | nuclei -t fuzz/

[ERR] Could not find template 'fuzz/': could not find template file: no such path found: fuzz/ [INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] Targets loaded for current scan: 2458 [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan

Before the latest update, it was running the scan normally.

Note: fuzz/ is the file where I put some specified YAML templates to scan.

It should be an absolute path problem. Use an absolute path to specify the templates directory works fine for me, instead of a relative path.

➜  ~ nuclei -t ./fuzzing-templates                                 
                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

                projectdiscovery.io

[ERR] Could not find template './fuzzing-templates': could not find template file: no such path found: ./fuzzing-templates
[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] No results found. Better luck next time!
[FTL] Could not run nuclei: no templates provided for scan
➜  ~ ls ./fuzzing-templates
cmdi  csti  LICENSE    redirect  sqli  ssti  xxe
crlf  lfi   README.md  rfi       ssrf  xss
➜  ~ nuclei -t /root/fuzzing-templates                             
                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

                projectdiscovery.io

[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] New templates added in latest release: 1
[INF] Templates loaded for current scan: 19
[WRN] Executing 21 unsigned templates. Use with caution.
[INF] No results found. Better luck next time!
➜  ~
pphuahua commented 1 year ago 
9:52:42 › sudo ./nuclei3 -t Template-Hub 

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

        projectdiscovery.io

[ERR] Could not find template 'Template-Hub': could not find template file: no such path found: Template-Hub
[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] No results found. Better luck next time!
[FTL] Could not run nuclei: no templates provided for scan
9:53:53 › sudo ./nuclei3 -t /Users/pphua/Template-Hub

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v3.0.1

        projectdiscovery.io

[INF] Current nuclei version: v3.0.1 (latest)
[INF] Current nuclei-templates version: v9.6.7 (latest)
[INF] New templates added in latest release: 1
[INF] Templates loaded for current scan: 600
[WRN] Executing 600 unsigned templates. Use with caution.
[INF] No results found. Better luck next time!

Use absolute paths, but not relative paths :(

Moskitoz commented 1 year ago

cat target.txt | nuclei -t fuzzing-templates/

                 __     _

__ ___/ / (_) / \/ / / / / / \/ / / / / / // / // / / / // //_,/\/_/__// v2.9.15

            projectdiscovery.io

[INF] Current nuclei version: v2.9.15 (outdated) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] New templates added in latest release: 1 [INF] Templates loaded for current scan: 18 [INF] Targets loaded for current scan: 3 [INF] Using Interactsh Server: oast.live [INF] No results found. Better luck next time!

as you see the nuclei -t fuzzing-templates/ works fine in v2.9.15

but in the last version when u run same cmd u will get

[ERR] Could not find template 'fuzzing-templates': could not find template file: no such path found: fuzzing-templates [INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan

DroidKali commented 1 year ago

cat target.txt | nuclei -t fuzzing-templates/

                 __     _

__ ___/ / (_) / \/ / / / / / \/ / / / / / // / // / / / // //_,/\/_/__// v2.9.15

            projectdiscovery.io

[INF] Current nuclei version: v2.9.15 (outdated) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] New templates added in latest release: 1 [INF] Templates loaded for current scan: 18 [INF] Targets loaded for current scan: 3 [INF] Using Interactsh Server: oast.live [INF] No results found. Better luck next time!

as you see the nuclei -t fuzzing-templates/ works fine in v2.9.15

but in the last version when u run same cmd u will get

[ERR] Could not find template 'fuzzing-templates': could not find template file: no such path found: fuzzing-templates [INF] Current nuclei version: v3.0.1 (latest) [INF] Current nuclei-templates version: v9.6.7 (latest) [INF] No results found. Better luck next time! [FTL] Could not run nuclei: no templates provided for scan

See above, use absolute paths. NOT relative paths. e.g. 

cat targets.txt | nuclei -t /root/fuzzing-templates

NOT ./fuzzing-templates

Moskitoz commented 1 year ago

Thanks for the special effort of the Nuclei developer team.

ehsandeep commented 1 year ago

This is fixed in https://github.com/projectdiscovery/nuclei/pull/4284 and will be part of next release.

ehsandeep commented 1 year ago

This is now fixed in latest release - https://github.com/projectdiscovery/nuclei/releases/tag/v3.0.2