search

R0X4R / Garud

An automation tool that scans sub-domains, sub-domain takeover, then filters out XSS, SSTI, SSRF, and more injection point parameters and scans for some low hanging vulnerabilities automatically.
MIT License
768 stars 176 forks source link

Stuck at subdomain scanning #51

Closed waelahmed-dev closed 2 years ago

waelahmed-dev commented 2 years ago

This is my first time using the tool. I just get stuck at subdomain scanning, I tried to leave it for about 3 hours and it was still stuck at the same phase, even I can't cancelling it by hitting ctrl + c, it won't cancel until I close my vps window 169668922-e6b6ce86-204f-4aad-ae1a-32fe9554a293

Any ideas where is the problem? Thanks in advance.

R0X4R commented 2 years ago

I think there's some issue with your amass try running your garud using and check where you get stuck and then let me know will fix it then. Also please share your vps specs and env

Command: 

$ bash -x /usr/bin/garud -d target.com
waelahmed-dev commented 2 years ago

this is the result:

Screenshot_2022-05-22_11-27-30

my vps specs: 2 GB RAM, 1 vCPU, 60 GB SSD Node.js

I don't think that it has an env, it's amazon lightsail instance Actually, the cpu usage is fixed at 100% while the tool is running, so does it require higher specs?

R0X4R commented 2 years ago

Yes it requires higher specs to work faster but the specs you mentioned here is okay. Try using Amazon EC2 instance I have no idea about Amazon Lightsail coz I have never run garud on it. Actually the issue is with the amass try commenting out the amass scans I'm pasting the line number and code below.

Run garud like this (use screen to let it run in background)

$ env bash
$ garud -d target.com

Line 146

# amass enum -passive -d $DM -o .tmp/amass.list &> /dev/null

Line 153

# timeout 50m amass enum -active -brute -w ~/wordlists/subdomains.txt -d $DM -o .tmp/amassact.list &> /dev/null