Browsers: February 2008 Archives

I've blogged before on how Gmail has an advantage over Yahoo Mail -- and most other Web-based e-mail services -- because you can choose to run a totally secure session (by entering the URL https://gmail.com instead of plain ol' http://gmail.com) and feel safe when reading and writing e-mail over public WiFi connections.

Seems it isn't so. According the Zero Day blog at ZDNet, somebody monitoring the radio traffic of your wireless connection can figure out your password through the use of unencrypted cookies with a technique called "sidejacking":

Sidejacking is a term (Robert) Graham uses to describe his session hijacking hack that can compromise nearly all Web 2.0 applications that rely on saved cookie information to seamlessly log people back in to an account without the need to reenter the password. By listening to and storing radio signals from the airwaves with any laptop, an attacker can harvest cookies from multiple users and go in to their Web 2.0 application. Even though the password wasn’t actually cracked or stolen, possession of the cookies acts as a temporary key to gain access to Web 2.0 applications such as Gmail, Hotmail, and Yahoo. The attacker can even find out what books you ordered on Amazon, where you live from Google maps, acquire digital certificates with your email account in the subject line, and much more.

Gmail in SSL https mode was thought to be safe because it encrypted everything, but it turns out that Gmail’s JavaScript code will fall back to non-encrypted http mode if https isn’t available. This is actually a very common scenario anytime a laptop connects to a hotspot before the user signs in where the laptop will attempt to connect to Gmail if the application is opened but it won’t be able to connect to anything. At that point in time Gmail’s JavaScripts will attempt to communicate via unencrypted http mode and it’s game over if someone is capturing the data.

What’s really sad is the fact that Google Gmail is one of the “better” Web 2.0 applications out there and it still can’t get security right even when a user actually chooses to use SSL mode. Other applications like Microsoft’s MSN/Hotmail and Yahoo don’t even have SSL modes. The fact that they use SSL mode for first time authentication and sign-in is irrelevant because they all drop down to unencrypted mode right after the user authenticates.

I don't use my DSL Extreme Web mail as often as I should. It has a secure connection the whole time, and it's primitive enough -- I hope -- not to have these same vulnerabilities. Fastmail.fm, on which I also have a free account, will also do a secure session if you choose "secure login" when signing on.

I'm far from a security expert, but it seems to me that we'd be in better shape if we had the option of running a Web browser in secure-server mode all the time.