Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Security The Internet Twitter Yahoo! IT

Twitter, Hotmail, LinkedIn, Yahoo Open To Hijacking 50

mask.of.sanity writes "Twitter, Linkedin, Yahoo! and Hotmail accounts are open to hijacking thanks to a flaw that allows cookies to be stolen and reused. Attackers need to intercept cookies while the user is logged into the service because the cookies expire on log-out (except LinkedIn, which keeps cookies for three months). The server will still consider them valid. For the Twitter attack, you need to grab the auth_token string and insert it into your local Twitter cookies. Reload Twitter, and you'll be logged in as your target (video here). Not even password changes will kick you out."
This discussion has been archived. No new comments can be posted.

Twitter, Hotmail, LinkedIn, Yahoo Open To Hijacking

Comments Filter:
  • by datajack ( 17285 ) on Friday March 22, 2013 @10:40AM (#43246435)

    I dodn't think my opinion of SC magazine could get any lower, then they publish this!

    Despite what TFA says, this is not a session fixation vulnerability, this is simple session hijacking - with the willing cooperation of the 'victim'.

    Session Fixation (for those who don't know the term) does not involve stealing the victim's session cookie at all. It is precisely the opposite :-
    * The attacker connects to the service without authenticating but creating an application session.
    * The attacker accesses the newly created session cookie and somehow (using whatever other vulns or methods available to them) manages to inject that into the victim's browser before they have logged into the target system.
    * The victim accesses the target system. their browser supplies the injected session cookie to the server and it is accepted as an existing session.
    * The victim logs in. If the target system is vulnerable to fixation, the victim has just authenticated the session that the attacker created.

    The protection against this is for the server to destroy the currently active session and create a new one at the point of successful authentication.

    Whilst there are mitigation techniques against session hijacking, they all have their own complications and problems and have varying degrees of effectiveness.
    keeping the session id cookie a secret between the user and server is a fundamental part of web security and a failure at this level has not been demonstrated here.

Software production is assumed to be a line function, but it is run like a staff function. -- Paul Licker

Working...