Skip to content
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

HunterHow - invalid memory address or nil pointer dereference #185

Closed
bongobongoland opened this issue Mar 29, 2023 · 9 comments · Fixed by #224
Closed

HunterHow - invalid memory address or nil pointer dereference #185

bongobongoland opened this issue Mar 29, 2023 · 9 comments · Fixed by #224
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@bongobongoland
Copy link

bongobongoland commented Mar 29, 2023

I'm getting the following when trying to run hunterhow:

$/home/kali/go/bin/uncover -q hunterhow.query -e hunterhow -l 1000 -o hunterhow.txt

[INF] Current uncover version v1.0.3 (latest)
[hunterhow] couldn't create new session: no default rate limit found for engine hunterhow
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xc9cbd8]

goroutine 36 [running]:
github.com/projectdiscovery/uncover/uncover/agent/hunterhow.(*Agent).Query(0xc0004b5350?, 0xe3f9d9?, 0xdd7d93?)
        /home/kali/go/pkg/mod/github.com/projectdiscovery/uncover@v1.0.3/uncover/agent/hunterhow/hunterhow.go:24 +0x18
github.com/projectdiscovery/uncover/runner.(*Runner).Run.func1({0x1031a70, 0x162eaf0}, 0xc00040e450?)
        /home/kali/go/pkg/mod/github.com/projectdiscovery/uncover@v1.0.3/runner/runner.go:184 +0x4af
created by github.com/projectdiscovery/uncover/runner.(*Runner).Run
        /home/kali/go/pkg/mod/github.com/projectdiscovery/uncover@v1.0.3/runner/runner.go:165 +0x1cdb

Am I missing something? Do I need to edit something?
Also, there's no HunterHow's key section in the provider-config.yaml file.

@bongobongoland bongobongoland added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Mar 29, 2023
@ehsandeep ehsandeep changed the title HunterHow - No default rate limit Error HunterHow - invalid memory address or nil pointer dereference Mar 29, 2023
@xm1k3 xm1k3 self-assigned this Apr 7, 2023
@Mzack9999
Copy link
Member

@bongobongoland I am unable to reproduce this issue as it probably got indirectly fixed as part of #201

$ uncover -q hunterhow.query -e hunterhow -l 1000 -o hunterhow.txt

  __  ______  _________ _   _____  _____
 / / / / __ \/ ___/ __ \ | / / _ \/ ___/
/ /_/ / / / / /__/ /_/ / |/ /  __/ /    
\__,_/_/ /_/\___/\____/|___/\___/_/

                projectdiscovery.io

[INF] Current uncover version v1.0.4-dev (dev)
[FTL] Could not run enumeration: [uncover:RUNTIME] agents [hunterhow] requires keys, but no keys were found

exit status 1

Could you check if you can still reproduce it with the latest version?
Thanks!

@bongobongoland
Copy link
Author

ok, getting a different output now.

[INF] Current uncover version v1.0.4 (latest)
[hunterhow] the optional range of page size is 10 20 50 100

@bongobongoland
Copy link
Author

so what do I do? :) please advise

@Mzack9999
Copy link
Member

Did you configure a key in provider-config.yaml? I'm getting this output with the command you provided

$ uncover -q hunterhow.query -e hunterhow -l 1000 -o hunterhow.txt

  __  ______  _________ _   _____  _____
 / / / / __ \/ ___/ __ \ | / / _ \/ ___/
/ /_/ / / / / /__/ /_/ / |/ /  __/ /    
\__,_/_/ /_/\___/\____/|___/\___/_/

                projectdiscovery.io

[INF] Current uncover version v1.0.4 (latest)
[FTL] Could not run enumeration: [uncover:RUNTIME] agents [hunterhow] requires keys but no keys were found
exit status 1

@bongobongoland
Copy link
Author

yeah, I have a key.

@bongobongoland
Copy link
Author

If I'm not mistaken,

[hunterhow] the optional range of page size is 10 20 50 100

is a response from hunterhow

@Mzack9999
Copy link
Member

@bongobongoland I'm not able to reproduce the issue. We can better investigate if you provide all the steps, queries, and configurations you use. For the record, I'm doing this:

$ cat providers.yaml
shodan: []
censys: []
fofa: []
quake:
hunter: []
zoomeye: []
netlas: []
criminalip: []
publicwww: []
hunterhow:
  - "xxx" # valid key
$ cat hunterhow.query
test
$ uncover -q hunterhow.query -e hunterhow -l 1000 -o hunterhow.txt -pc providers.yaml

  __  ______  _________ _   _____  _____
 / / / / __ \/ ___/ __ \ | / / _ \/ ___/
/ /_/ / / / / /__/ /_/ / |/ /  __/ /
\__,_/_/ /_/\___/\____/|___/\___/_/

                projectdiscovery.io

[INF] Current uncover version v1.0.4 (latest)

@Mzack9999 Mzack9999 self-assigned this May 18, 2023
@bongobongoland
Copy link
Author

bongobongoland commented May 22, 2023

put anything other than test in your query file.

try the following line:

ip.port=="666" and ip.country=="US"

@Mzack9999 Mzack9999 linked a pull request May 23, 2023 that will close this issue
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label May 24, 2023
@ehsandeep ehsandeep added this to the uncover v1.0.5 milestone May 24, 2023
@ehsandeep
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants