-
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
panic: runtime error: invalid memory address or nil pointer dereference #4025
Comments
I have the same
|
@mastercho, |
For me happens on random bases |
Reproduced on Gitlab:
Deps:
Stderr: panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x11cde1d]
goroutine 106600 [running]:
github.com/projectdiscovery/dsl.init.0.func73({0xc0035fde00, 0x3, 0x16?})
github.com/projectdiscovery/[email protected]/dsl.go:852 +0x35d |
We hope this problem to be resolved in the upcoming release. I will keep you informed. |
Can you try the new release and see if the issue has been resolved? |
The issue hasn't been solved nuclei v2.9.11
|
Hello @ViCrack, I would like to verify if you are experiencing the same error when using the command |
Hello @dogancanbakir OS: Centos7 My command : and the test.txt file has a large number of lines (3000+) This issue occurs randomly |
Indirectly fixed via projectdiscovery/dsl#80 |
This is issue is now fixed in |
@mastercho you can take a look at the code changes - projectdiscovery/dsl#80, this is now fixed in the latest nuclei release. @ViCrack @storenth ^ |
Nuclei version: 2.9.10
Current Behavior:
Every time when i try to run scan getting
Thought is RAM issue but after testing on 3 more machines can confirm is a bug
Expected Behavior:
To finish scan without issue
Steps To Reproduce:
nuclei -l test.txt -s critical
The text was updated successfully, but these errors were encountered: