[ad]<\/p>\n
You may or may not have noticed, but I was on hiatus for a few days. As you’re probably aware (and I’m sure many of you celebrate) it was Chinese New Year on February 14th so I was offline for a few days taking a well deserved break.<\/p>\n
I’d like to wish all of you that celebrate it a Happy Chinese New Year.<\/p>\n
Anyway the big news during this period, especially in the whole social networking scene has been Google Buzz<\/a>. Is the next challenger to Twitter<\/a> or Friendfeed or even Facebook<\/a>? Personally I think not, but it sure has got people talking.<\/p>\n Google has fixed a cross-site scripting bug that allowed attackers to take control of Google Buzz accounts. The bug affects the mobile version of Buzz and was reported Feb. 16 by SecTheory CEO Robert Hansen. Google patched the vulnerability the same day. According to Hansen, news of the flaw was passed along to him by a hacker with the moniker of TrainReq.<\/p>\n “There [are] four things of note here,” Hansen blogged. “Firstly, it’s on Google’s domain, not some other domain like Google Gadgets or something. So, yes, it’s bad for phishing and for cookies. Secondly, it’s over SSL\/TLS [Secure Sockets Layer\/Transport Layer Security] (so no one should be able to see what’s going on, right?). Third, it could be used to hijack Google Buzz\u2014as if anyone is using that product (or at least you shouldn’t be). And lastly, isn’t it ironic that Google is asking to know where I am on the very same page that’s being compromised?”<\/p><\/blockquote>\n The news from the last few days included a cross site scripting<\/a> flaw in the mobile version of Google Buzz.<\/p>\n It was fixed promptly because the guy that discovered it was kind enough to tell Google about it.<\/p>\n As always though if something was discovered so quickly and reported so quickly how many more flaws are there being used by the bad guys out there.<\/p>\n Hansen was referring to the location feature in Buzz that shows where Buzz users are when they post. This feature can be turned off by the user.<\/p>\n “We have no indication that the vulnerability was actively abused,” a Google spokesperson said. “We understand the importance of our users’ security, and we are committed to further improving the security of Google Buzz.”<\/p>\n In the week since Buzz was launched Feb. 9, Google has faced criticism over privacy issues associated with the service. On Feb. 16, the Electronic Privacy Information Center filed a complaint with the Federal Trade Commission that charged Google with failing to protect users’ privacy. In an interview with eWEEK, Google Vice President of Product Management Bradley Horowitz said the company did not expect the negative response that Google Buzz received on the privacy issue.<\/p><\/blockquote>\n There was also a big outcry about privacy when Buzz was launched due the fact it automatically populates your following list with people you often converse with.<\/p>\n Imagine if you’d been hunting for a new job and talking to someone from a competitor and your boss saw it? Or a husband chatting with another woman and his wife saw who he was ‘following’? There are a lot of permutations, all of which are not good so use your imagination.<\/p>\n eWeek also did another article about the privacy concerns here – Buzz Privacy Backlash<\/a>.<\/p>\n <\/p>\n