Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Security

SSL Renegotiation Attack Becomes Real 97

rastos1 and several other readers noted that the SSL vulnerability we discussed a couple of weeks back, which some researchers had claimed was too theoretical to worry about, has now been demonstrated by exploit. The attack description is available on securegoose.org. "A Turkish grad student has devised a serious, real-world attack on Twitter that targeted a recently discovered vulnerability in the SSL protocol. The exploit by Anil Kurmus is significant because it successfully targeted the so-called SSL renegotiation bug to steal Twitter login credentials that passed through encrypted data streams. All in all, a man in the middle is able to steal the credentials of a user authenticating himself through HTTPS to a trusted website."
This discussion has been archived. No new comments can be posted.

SSL Renegotiation Attack Becomes Real

Comments Filter:
  • Kinda bad summary (Score:5, Insightful)

    by Virak ( 897071 ) on Monday November 16, 2009 @07:53PM (#30123856) Homepage

    Important part of the article:

    He did it by injecting text that instructed Twitter's application protocol interface to dump the contents of the web request into a Twitter message after they had been decrypted.

    The only reason it was exploitable was because of Twitter's API. Understandably, I'm not too worried about the rest of the Internet going down in flames any time soon.

  • by teh_commodore ( 1099079 ) on Monday November 16, 2009 @07:58PM (#30123898)
    Oh good. We're totally fine. It only works on sites that are poorly designed. And Twitter's been patched, so that leaves, well, I guess no one.
  • The sky is falling (Score:4, Insightful)

    by LBt1st ( 709520 ) on Monday November 16, 2009 @09:42PM (#30124782)

    It would be nice if FireFox updated with detection for sites that would allow this (and other) kinds of attacks.
    With shit like this in the wild it's hard to know what sites to trust. /Paranoid

  • by Anonymous Coward on Monday November 16, 2009 @10:06PM (#30124918)

    You are forgiven for the error. Anyone using a letter that could be mistaken for a number in any software version string should be cockpunched with brass knuckles coated in broken glass and lemon juice

  • by Frosty Piss ( 770223 ) on Monday November 16, 2009 @10:07PM (#30124930)

    It would be nice if FireFox updated with detection for sites that would allow this (and other) kinds of attacks.

    FF already nags enough.

  • by Anonymous Coward on Monday November 16, 2009 @10:10PM (#30124948)

    No it just means they will arrest him and throw him in jail next time he visits the USA on holiday.

  • by socceroos ( 1374367 ) on Tuesday November 17, 2009 @12:27AM (#30125740)
    People ought to stop blaming "The Web" as being inherently insecure. As much as you drill down into it, when party1 communicates with party2 and party1 isn't intimately familiar with party2's identity then transactions of information will always be prone to being exploited. This goes for human interaction (face to face) as well as human-to-computer interaction.

    Frankly, I'd rather have an insecure internet than have an internet where everyone's identity was fully exposed and documented.
  • by Lennie ( 16154 ) on Tuesday November 17, 2009 @12:41PM (#30130346)
    You have to remember it's not a fix. It's a workaround, it just disables part of the protocol.

    Their are also new packages for Apache2 for Debian for some other parts that needed to be disabled/changed, but it too is just a workaround.

    Their isn't yet a real fix, because it's problem with the protocol it self.

This file will self-destruct in five minutes.

Working...