Slashdot Mirror


'Bar Mitzvah Attack' Plagues SSL/TLS Encryption

ancientribe writes Once again, SSL/TLS encryption is getting dogged by outdated and weak options that make it less secure. This time, it's the weak keys in the older RC4 crypto algorithm, which can be abused such that an attacker can sniff credentials or other data in an SSL session, according to a researcher who revealed the hack today at Black Hat Asia in Singapore. A slice: Bar Mitzvah exploits the weak keys used by RC4 and allows an attacker to recover plain text from the encrypted information, potentially exposing account credentials, credit card data, or other sensitive information. And unlike previous SSL hacks, this one doesn't require an active man-in-the-middle session, just passive sniffing or eavesdropping on SSL/TLS-encrypted connections, [researcher Itsik] Mantin says. But MITM could be used as well, though, for hijacking a session, he says.

8 of 23 comments (clear)

  1. 'Bar Mitzvah Attack' Plagues SSL/TLS Encryption by ArcadeMan · · Score: 3, Funny

    But only on Jewish websites.

    I kid, of course. Mel Brooks rules!

  2. Re:Duh by Dragonslicer · · Score: 4, Interesting

    It's been well over a decade since the weaknesses of RC4 have been widely disseminated. No surprises here.

    The summary fails to mention (anyone surprised?) that this is where the name comes from. Apparently the flaws have been known for 13 years.

  3. Re: 'Bar Mitzvah Attack' Plagues SSL/TLS Encryptio by Anonymous Coward · · Score: 5, Funny

    I hear the attack cuts your connection a little shorter.

  4. I miss vulns with CVE numbers or bug tracker IDs. by mr_mischief · · Score: 4, Insightful

    I really hate how every little thing gets some catchy marketing name now that is hard to search. Just give me the damn CVE.

  5. Re:Duh by thegarbz · · Score: 4, Informative

    The flaws in RC4 have been known about for a long time but were thought irrelevant in the scheme of SSL/TLS to the point where RC4 was the preferred cipher suit only a few years ago as it was one of the few that were able to mitigate the BEAST attack. So the GP's comment that there's no surprise since RC4 has been known to be weak for a decade isn't quite the full story.

    It was only in 2013 where RC4 became strictly taboo for use in SSL/TLS with the exposure of new exploitable vulnerabilities on top of the several previous weaknesses identified, and last month RFC7465 effectively banned the cipher's use in TLS.

  6. CipherList by manu0601 · · Score: 2

    Good CipherList for OpenSSL based applications: ECDH@STRENGTH:DH@STRENGTH:HIGH:!RC4:!MD5:!DES:!aNULL:!eNULL

    Next step is to add !3DES

  7. why not saying only simply attack on RC4 by ruir · · Score: 3, Funny

    Tired of bullshit names....what next, the Lewinsky attack on Linux?

  8. Slashdot from 2013 calling :) by DougPaulson · · Score: 3, Interesting

    "Dan Bernstein presented a method for breaking TLS and SSL web encryption when it's combined with the popular stream cipher RC4 invented by Ron Rivest in 1987", Thursday March 14, 2013