2 ms·
"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 informat
by 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.