Google bugs stories and the shiny pixelbook.
Peace upon you hunters, hope y'all doing good, My gift from google security team has landed today, Here I am sharing the bugs that got it for me, along the past year (2017) which also ranked me at 7 onto google HOF, anyway, there is nothing special about them, but folks wanted to see them.
2) business.google.com Stored XSS:
if you ever hunted in business.google.com then you have seen that they got an option
for editing the website of your business location, what you'll be sure of website editing is
always ability to inject at least tags like
3)changing your home temperature through leaking your nest access token in referer:
one day i was checking my phone (android device),seen that they wanted to push an update which was the google assistant
with her lovely voice lol, after the the assistant installed I ran burpsuite up and start looking around the app and i was
lucky that there were too much things to play with.
in google assistant you can control your smart home devices by linking third parties (the ones that control your smart
home's devices), what cought my attention in there is "nest" app, as its owned
by google and other are just third parties and wont be rewarded,
the attack flow was as follow:
4) google Local Guides Stored XSS via AngularJS Injection: if you used to share reviews, photos, about the places in google maps then you are familiar with google Local Guides product, at some certain level, google will offer you to create a meetup, creating the meetup with angularjs exprestion in name of the meetup was stored and exectued back. contribute whenever you can with google.
5) google maps reflected XSS: this one was also related to google Local Guides but diffrent root, like every hunter, I have multiple google accounts, at one point, I was trying to access a url from account with creating meetup privilege with account without that privilege and then something interesting show up on screen. a url with paramter and value, i didnt use to see, espcially when you are familiar with google vrp. the value was reflected back nacked , i mean without sanitizing special characters. so the vulnerable url was something like : google.com/maps/apis/authen?par=XSS-goes-here. I forgot to take any screenshots or record the POC, and deleted the report email. beside my account in google local guide has blocked by a google staff. lesson learn here is, always check apps,links,features with low preveillge account espcilally with Google VRP, you got no idea what'll show up.
6) explorer.earthengine.google.com reflected XSS IE only:
this XSS's found after reading @cure53berlin's resaerch shows a trick how to do that. their research is a treasure i highly recommend reading
this was a self-stored XSS till i discovered that the adding the data was lacking the CSRF protection,combining thse minor issues:
these bugs were all i could collect, still there two or three high-bounty bugs but i couldnt find them, i hope you didnt get bored reading it. i highlighted some advices that helps you with google vrp, i would like to thank google security team,especially @sirdarckcat this guy is a strong bridge between hunters and google vrp, just leave us a comment if you feel to at @missoum1307 peace upon you.