@GASTONDERECK Well thereโs no for sure way. If it is reflecting something that you provided start giving it weird values like XSS payloads or try CRLF injections or really long values. Basically just start giving it unexpected inputs and see if anything interesting happens.
I havenโt done much BB in months but I just got $1k for an info disclosure and I have a cache poisoning XSS being worked on ๐ taking a break seems like it helped me focus
I finally got ffuf to output to a text file in a decent way for automation:
ffuf -w /tmp/wordlists.txt -u URL/FUZZ -r -ac -v &>> /tmp/output.txt ; sed -i 's/\:\: Progress.*Errors.*\:\://g' /tmp/output.txt ; sed -i 's/\x1B\[[0-9;]\{1,\}[A-Za-z]//g' /tmp/output.txt
#bugbounty
@0x8sksr Unfortunately no, but I would still run directory brute forcing with the .sh extension and the .php extension to see if you can find anything additional
If you find an API key in JS or somewhere else but aren't sure what calls it goes to you can try this:
gau https://t.co/QMHZrZ41Xs | httpx -silent -mc 400,401,403 | httpx -mc 200 -path "?apikey=keyhere"
#bugbountytip#bugbountytips#bugbounty#apihacking
@0x8sksr It really depends. Look through the shell scripts for hard coded secrets tokens etc. also look for other scripts referenced in there and see if you can access those. You may also want to do a directory brute force with the .sh extension to check for additional scripts.
Does anyone else have any automation and do you ever get any bounties from it? Iโm trying to beef mine up to do more than sub domains and XSS #BugBounty
Hmmm I went to read the documentation about an interesting site I found and this is literally in there ๐ I guess I have to try it now #rtfm#BugBounty