How I found my first ever bug.

You have probably clicked after the title, cuz you also want to find more bugs or your first bug, Lets get started!!

I will keep the website’s identity hidden.

Introduction:

Recently I was searching for my new bug bounty program to hunt on, I went to openbugbounty.org to find a target where I discovered a program, it was quite good, the website wasn’t based on WordPress :) so I chose it as my new target.

openbugbounty.org bug bounty programs lists

So after that I just hoped for finding an information disclosure in it.

So I fired up my katana and entered the URL of my target to get all JS files of the target’s URL.

katana -u website.com Results from katana

Yeah, after getting my JS files from Katana and saving them in a .txt file I fired up SecretFinder to fetch all vulnerable information from JS files fetched from Katana.

I used the following command.

cat {jsfilesgottenfromkatana.txt} | while read url; do python3 SecretFinder/SecretFinder.py -i $url -o cli; done

And after that I found some interesting information from SecretFinder.

Results from SecretFinder…Google API (in red box)

I was very very happy but wait….Is it really vulnerable?

To find if a google maps API key is vulnerable or not I recommend you a tool called gmapsapiscanner on GitHub.

After installing it do the following.

cd gmapsapiscanner
python3 maps_api_scanner.py

And enter the API you want to test.

Remember that Google Maps API key is paid, and if it is misconfigured then it can cause potential financial damage to the organization owning the API key.

As you can see the API key is vulnerable to Staticmaps and Streetview, means that anybody can fetch requests from the API, it gave me two links and after manual testing it was confirmed that the API key was vulnerable and was not properly configured.

fetching request from API key (streetview map)fetching request from API key (staticview map)

So after manually testing I reported it on openbugbounty.org and sent them an email directly.

But it is still under manual testing status.

openbugbounty.org submission status

Reported on: March 1, 2024

Hoping a response from them.

I hope this blog helped you in finding your first bug or a new bug!

Don’t forget to follow me, for more amazing blogs! Thanks for your support on my previous blog!