Search for a command to run...
I'm an App Developer, Security Researcher and Designer living in Phoenix, Arizona. In the past I've worked with Apple, Zoom, Axon, Starbucks and many more great companies. My security and app dev work has been featured in the press – Bloomberg, Techcrunch, and many more.
No comments yet. Be the first to comment.
This is my second bug bounty - a bug that I discovered while messing around on a Facebook group. It was my freshman year at ASU, and I was administering this Facebook called "The Great Indian Dream, Class of '23" – a group dedicated to Indian high sc...
Writeup for Google CTF's Mindreader Challenge from 2017.
It was the end of my Grade 12th Preboard exams and I needed something to destress, and what better way to destress by bug hunting (atleast after doing something as awful highschool exams).
Typically, I just browse through the apps on my phone and start looking for my next target everytime I bug hunt. This time I thought it should be something different than the Facebook family of apps.
Instead of reverse engineering their app, I took different approach this time. I decided to take a look at their corp servers instead. I recently came across shodan.io which is a database of connected devices.
That's cool and all, but one of the coolest part about Shodan is that they also let you apply pretty specific filters. These filters even work to search for metadata within SSL certificates. I used this to filter by "Common Name" as *.shazam.com and shazam.com and happened to find a couple servers on their network.
My first instinct was to test these for heartbleed - one of the most trending vulnerabilities from 2014. To my surprise, they turned to be vulnerable to heartbleed - even in 2017!
I sent out this report to Shazam and within a couple days got a response from the team with the bug bounty notification.
Incredibly grateful to Shazam for this bug bounty, even though they didn't have an established bounty program at that time (this is all before the Apple acquisition).
Timeline:
Initial Report – Jan 23, 2017
Initial response from Shazam – Jan 24, 2017
Bounty Awarded – Jan 26, 2017