” how to hack Google ?” is probably one of the most interesting questions that any hacker may ask from himself. Hackers have always been on the lookout for ways to hack Google and its tools. Now, it seems that some have managed to find their way. One of the tools that Google uses to get feedback from its audience was declared vulnerable recently. These vulnerabilities can be exploited by hackers, so attackers can literally steal your data.
If you were sure that the question of how to hack Google Docs is complicated, it is good to know that stealing occurs only by taking screenshots of sensitive Google Docs documents. Easy and simple. Therefore, important files that you have saved in Google Docs are in danger of being exposed. All it takes is the process of embedding the files on a malicious website.
This vulnerability was discovered by Sreeram KL as part of Google’s bug bounty on the 9th of July. Sreeram KL was rewarded with $ 3133.70 after discovering this vulnerability.
The key to answering how to hack Google
Google Docs, just like many other Google tools, has a feature of monitoring users’ feedback. These features are known as “Send feedback” or “Help Docs improve”. “Send feedback” operates based on what users send as a report. Users’ report may contain screenshots to highlight specific issues.
The entire network that receives users’ reports through different Google tools is integrated, which appears on different platforms via an iframe element that loads the pop-up content from “feedback.googleusercontent.com”. In other words, whenever your report contains a screenshot, the RGB values of every pixel would be forwarded to google.com. RGB values later get encrypted by the parent domain in Base64 encoded format. Eventually, the parent domain sends back encrypted values to the “feedback.googleusercontent.com”. That tells us how to hack Google.
Sreeram is the one who has found the answer
It seems that “Sreeram” knows how to hack Google Docs. The vulnerability that “Sreeram” has found creates a security gap on the path of redirecting values to “feedback.googleusercontent.com”. The security gap lets hackers steal the screenshots that you upload to the feedback domain. So whenever you submit a report to Google servers, your reports are potentially at the risk of being hijacked.
The vulnerability arises from a lack of X-Frame-Options header in the Google Docs domain. As a result, attackers can convert the target origin of the messages that have been sent. Therefore, the cross-origin communication that has been created between the page and the frame contained in it turns to be exploitable, and boom… you just found out how to hack Google Docs.
What is X-Frame-Options?
Being aware of the lack of X-Frame-Options tells us how to hack Google Docs. But what is X-Frame-Options and why is it important for us? X-Frame-Options does make embedding contents into other sites impossible. There, using X-Frame-Options reduces the risk of clickjacking attacks.
The most important element that poses threat to the users is the engaging process of sending feedback. If the process of submitting feedback was not engaging enough to make clients send feedbacks, no one could exploit their data..
A brief explanation about how to hack Google Docs
The entire process we have described here can take place easily by embedding a Google Docs file in an iFrame on a rogue website. Therefore, data would be directed to the domain that attackers choose, instead of “feedback.googleusercontent.com”.
Generally, if a partner domain does not provide a target origin during the cross-origin communication, disclosed data may be exploited and sent to any website. What exactly tells us how to hack Google Docs. As Mozilla documentation states:
“Always specify an exact target origin, not just when you use postMessage to send data to other windows. A malicious site can change the location of the window without your knowledge, and therefore it can intercept the data sent using postMessage