3 ms·
Even SSL Gmail can get sidejacked
- tarkin2 19y ago"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." I'm sure this sentence just flowed in the author's head, but what? It's a pity because this is the most crucial sentence in the article.
- dkokelley 19y agoI think what it means is that if you have an application that logs into gmail (either as a home page when you open your browser, google talk or other compatible client, or an email client such as outlook) automatically (after you've connected to the network but before you're connected to the internet) the application will try again, disabling ssl to see if that works. After you've finally connected to the internet, your application will log in to Gmail and open a session in Gmail without ssl. Then someone who is monitoring the unencrypted data will be able to sidejack your session. I'm pretty sure this is how it works, but correct me if I'm wrong.
- tarkin2 19y agoThat sounds about right, thanks; however it depends on the extant client-side javascript reverting to http while you're not connected to the internet, as pmjordan said.
- pmjordan 19y agoYeah, I wish he'd been clearer about that. I'll take a stab at deciphering it though: You've just connected your laptop's wifi to a hotspot (i.e. associated with the access point) but haven't yet logged in/paid. Connection attempts will now either re-route to the hotspot operator's login page or just fail, depending on how the hotspot is set up. Now, suppose, for whatever reason, gmail is still open in your browser from a previous session or whatever. It will keep trying to connect to the server via https, which fails as there's no route to it, and (according to the article) fall back to http. (which will also fail, but can be intercepted) I don't see how this will work unless you've still got the gmail client-side scripts executing from your browser's cache. Simply navigating to https://gmail.com/ https://gmail.com/ will fail, and the retry/redirect won't ever happen. Disclaimer: I don't know the inner workings of gmail; I've never looked into how gmail works at all. Edit: spelling
- tlrobinson 19y ago"Sidejacking is a term 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." and "Web 2.0 is fundamentally insecure because data isn't encrypted" Uh no, many "web 1.0" (and 1.2, 1.5, 1.6, 2.6, 3.0, AND 3.3... but not 1.8 or 2.5) sites are also vulnerable... it has nothing to do with a particular version of the interwebs. Anyway, from Robert Graham's article it sounds like XMLHttpRequests that are normally protected by SSL will fallback to non-SSL in the case of failure. Normally that should never happen, since http and https are considered different "origins" in terms of the same-origin policy. I couldn't tell if this is a browser issue, or if Gmail is doing something crazy. Either way, it's a big problem and should be fixed.
- pmjordan 19y ago"Which webs?" - "All of them." http://www.penny-arcade.com/comic/2007/07/16 http://www.penny-arcade.com/comic/2007/07/16
- imsteve 19y agoCould you put your ssl stuff on a different subdomain to prevent the browser from doing this?
- tlrobinson 19y agoSubdomains are also considered different origins. There are other ways around it, like using <script> tags. As far as whether or not that would prevent falling back to non-SSL, I doubt it.
- imsteve 19y agoBut if it can't make the connection to a non-SSL server on that domain then it can't send a cookie, I'd think. Unless it falls over to the non-subdomain.
- brlewis 19y agoI think gmail is purposefully making http/https both work. I seriously doubt there is a browser issue. Login cookies for ourdoings.com are secure-only, and AFAICT no browsers fail to handle them correctly. And you're right, this is not an issue limited to AJAX.