I’m always against companies data housing your information… I think your information should be kept to yourself and not be trusted with anyone else… but a recent XSS exploit found in Google just shows what can and will (Some day on a large scale – if it hasn’t already) happen….
read:
Universal XSS Vulnerability in all Google Services can compromise your personal information May 8th, 2009 Vulnerability Reported: 04/18/2009 9.33 pm Google’s Response: 04/18/2009 10.19 pm (Wow! that was super fast for Saturday :)) Vulnerability Fixed: 05/05/2009 7.05 pm Change Propagated: 05/07/2009 3.19 pm I recently reported a cross-scripting flaw to Google, which is now fixed. The vulnerability existed in Google’s Support Python Script where a malicious url is not sanitized for XSS character ‘ (single quote) before putting inside JavaScript variable logURL. As a result, it was possible to break the encapsulation of the var declaration and execute arbitrary JavaScript commands on the main Google.com domain. The only limitation was the following characters were either filtered out or url encoded - ” (double quote) < > (space) { }. However, this protection could be easily circumvented. I was able to write JavaScript statements to steal the session cookies [since characters such as ' ; . ( ) / = + were still available] and send it to my evil website. See the example given below. Your Google.com domain cookie is the central Single Sign-On cookie to all Google services. Once anyone gets it, he or she can use it to 1. Steal your emails. 2. Steal your contacts. 3. Steal your documents. 4. Steal your code. 5. Steal your sites. 6. Steal your website analytics. 7. Backdoor your iGoogle Homepage with malicious gadgets. …. and there should be still some more things remaining that you can play with.
Universal XSS Vulnerability in all Google Services can compromise your personal information
May 8th, 2009
Vulnerability Reported: 04/18/2009 9.33 pm
Google’s Response: 04/18/2009 10.19 pm (Wow! that was super fast for Saturday :))
Vulnerability Fixed: 05/05/2009 7.05 pm
Change Propagated: 05/07/2009 3.19 pm
I recently reported a cross-scripting flaw to Google, which is now fixed. The vulnerability existed in Google’s Support Python Script where a malicious url is not sanitized for XSS character ‘ (single quote) before putting inside JavaScript variable logURL. As a result, it was possible to break the encapsulation of the var declaration and execute arbitrary JavaScript commands on the main Google.com domain.
The only limitation was the following characters were either filtered out or url encoded - ” (double quote) < > (space) { }. However, this protection could be easily circumvented. I was able to write JavaScript statements to steal the session cookies [since characters such as ' ; . ( ) / = + were still available] and send it to my evil website. See the example given below.
Your Google.com domain cookie is the central Single Sign-On cookie to all Google services. Once anyone gets it, he or she can use it to
1. Steal your emails.
2. Steal your contacts.
3. Steal your documents.
4. Steal your code.
5. Steal your sites.
6. Steal your website analytics.
7. Backdoor your iGoogle Homepage with malicious gadgets.
…. and there should be still some more things remaining that you can play with.
Hi, I'm Stu. I launched this website to host some of the applications I have developed using C#. I'm always looking for new ideas, contact me if you have any :)