

I mentioned it before: because of the single-sign-on Google Account framework, every individual Google product has the power to introduce security or privacy vulnerability issues in other, unrelated Google products, or with the Google account in general. This current case is relatively harmless as it’s “only” a privacy issue and not a security issue, but it’s another example of the problem field. Whenever Google releases something on google.com, we must be aware that it doesn’t matter if it’s considered an Experimental, Labs, Alpha or Beta product by the engineers who created it... it’s still able to tamper with the almighty Google cookie.
Update: Google informed me that they fixed the bug now. My tests show this seems to be the case indeed – I can’t reproduce the privacy vulnerability anymore. [Thanks Sam!]
Update 2: TomHTML in the comments says the privacy vulnerability, albeit in another form, is still there. [Thanks TomHTML!]
>> More posts
Advertisement
This site unofficially covers Google™ and more with some rights reserved. Join our forum!