Today we will start hacking the application we selected yesterday.
In my case it was farmOS - you might have choosen a different Open Source Software you found on github - which is fine, the methodology is the same.
What to do first?
Right, start the application…
Recap:
We installed @Docker so that we can automagically have it running without headaches.
Now make sure that docker is running and type
docker ps
into your terminal. Your output should look similar to this one (the CONTAINER ID, PORTS and NAMES might look differently)
Good now go to your web browser and type
localhost
You might be greeted with this error - I just refreshed the page and it was gone - MAGIC! 🪄
Next we need to select a database:
I choose SQLite which is a database that consists of a single file on the disk.
Really smooth and easy to setup - one click and done.
Save and continue
now farmOS installs itself...
and asks us which modules we want to select...
since I have no idea what all the modules do, I just select ALL OF THEM 😅
Save and continue
We are almost finished
Now we hack. 🏴☠️🏴☠️🏴☠️
Question 1:
What do we look for?
Answer 1:
We need to understand what we are looking at here - so let's find out the tech stack first
What is the one thing that separates newbie bug hunters from the professionals - let me tell you
It’s persistence. The tools and ideas that for example @Jhaddix shows is his talks are far beyond the level I thought someone would use for Bug Bounty.
There was one Technique that blew my mind 🤯
It is scraping cloud provider IP ranges (proactively and recurring)
Imagine you are hacking on a program and you want to check which assets they have.
I assume at least 99% of what’s running on the web now is hosted by Cloud Providers (AWS, Azure, GCP, Digital Ocean etc)