nuclei: [issue] runtime error

Describe the bug I updated my nuclei install to version 2.4.1 and now it errors out every time i try to run it. Be advised I think upgrade over brew install and i am running Darwin HQSML-1689616 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_64. This is related to #888

Nuclei version Please share the version of the nuclei you are running with nuclei -version See above and below

Screenshot of the error or bug please add the screenshot showing bug or issue you are facing.

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   2.4.1

		projectdiscovery.io

[ERR] Could not read nuclei-ignore file: open /Users/gbiago909/.config/nuclei/.nuclei-ignore: no such file or directory
[INF] Using Nuclei Engine 2.4.1
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x49052fb]

goroutine 1 [running]:
github.com/projectdiscovery/nuclei/v2/internal/runner.(*Runner).RunEnumeration(0xc0000e6000, 0x0, 0x0)
	github.com/projectdiscovery/nuclei/v2/internal/runner/runner.go:345 +0xd5b
main.main()
	command-line-arguments/main.go:30 +0x87

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 39 (14 by maintainers)

Most upvoted comments

@forgedhallpass it seems to haave gone away since I updated. I dont know what happened it just started working so we are good to go

gbiagomba on Oct 15, 2021

@forgedhallpass the fix from my perspective (AWS Lambda function running inside golang Docker container) was to copy /root/.config to the root folder, and adjust the HOME env var:

RUN cp -R ~/.config /
ENV HOME=/

That resolved the issue I was seeing - but I think the author’s issue was slightly different.

terryf82 on Oct 11, 2021

Hello @gbiagomba,

With regards to your previous comment with regards to upgrading to 2.5.0, please note the following:

[WRN] Could not update templates: could not write template configuration: open /Users/gbiago909/.config/nuclei/.templates-config.json: permission denied
[ERR] Could not read nuclei-ignore file: open /Users/gbiago909/.config/nuclei/.nuclei-ignore: no such file or directory

It seems that you have some permission issues in you environment.

We have introduced stricter template validation in v2.5.0 that will give out warnings if the templates on your machine contain errors. The errors within the public nuclei-templates directory have been fixed prior the release, hence after a successful update, you should not see such warnings anymore.

p.s. in your last comment, you haven’t inserted the full execution log (only the banner and the disclaimer), hence I am not sure what problems are you referring to.

forgedhallpass on Sep 6, 2021