16th Acknowledgement From Google

Welcome everybody! I hope you wonderful people are doing great and street to Ethical Hacking is going straight. I believe past September and this Hacktober is a standout amongst other months in my hacking career. Learnt couple of more things and cleared some of my misguided concepts. Joined CoderStack as a tutor to guide other individuals about the risk and significance of Cyber Security and Ethical Hacking.
How magnificent it’s heard when somebody say “I Hacked Google”. Indeed I hacked google. I am not saying I bargained Google security but rather there was a security misconfiguration in one of it’s acquisitions which can used to pick up unauthorized access to users information.

When I took step in Cyber Security I wished to highlighted in Google in the rundown of security people and groups who actually helped Google for finding and revealing security vulnerabilities to Google and it’s acquisitions. The genuine joy is when dream works out as expected. A day I got highlighted, let me share a story with you, Hang tight!

FameBit is acquisition of google which is is an online marketplace that connects YouTubers with brands that are interested in advertising their products and services. This provides creators an opportunity to earn money with their content by partnering with brands that are relevant to their audience.

Noted FameBit to my sticky notes to play out a security test on it  later. As I kicked time I started testing it and in the wake of playing with it’s requests I established some security flaws which were related to Session Management and Authentication. We should brief them minimal more.

Session Management: In this security vulnerability, I have figured out how to login any individual to the attacker account in this manner, when any user logged in to attacker account, the attacker can see the user activity inside attacker account. For example, sensitive information and more. The issue depends on registration confirmation together with the password reset.

Steps to Replicate: 

  1. Attacker registered his account.
  2. Account registration confirmation mail will send to the attacker’s email.
  3. Attacker send the registration confirmation link to user.
  4. As user taps the link and he will automatically signed in to the attackers account.
  5. All done, user will surmise that he is in his own account but actually he is in attackers.

I observed that the password key creation was not enforced on the registration form and this will causes the issue on the both endpoints (enrollment and reset password).

I composed a point by point report and provided to Google security team and they triaged it and began taking a look at it. It took half month to decide it and move over a fix. Following fifteen days, I got mail from google that they fixed the security issue.Google Reply

After that I visit my Google VRP profile with a lot of expectations and then I noticed that I’ve been included on Google Security researchers hall of fame page . I truly commend that minute. This celebration can be considerably greater if report is qualified for bug bounty. Yet I have no stresses. I’ll attempt better fortunes next time 🙂Google Hall of Fame

Thanks for taking time, I truly value that. I look forward to see you there again soon enough. I require a recommendations from you wonderful peoples. I’m wanting to make a course on Ethical Hacking and IoT Hacking. Let me know in case you’re interested in Ethical Hacking or IoT or technology related stuff. Don’t hesitate to subscribe our NewsLetter. Feel free to comment and let me know what are your thoughts.

, , , , , , , , , , , , , , , , , , , , ,

One Comment

  1. Syed Adil

    I Am Amused By Your Work And Your Achivements. I Am Hoping That You Will Succeed Like Mark Zuckerberg And Bill Gates :p

    Jokes Apart!
    May Allah Give You Success In Every Field Of Your Fucking Life.

    Regards:( Jerry D.Suza )

Leave a Comment

Thanks for downloading!