SSL/TLS Vulnerability Details to be Released Friday

Published: 2011-09-20
Last Updated: 2011-09-20 15:18:13 UTC
by Kevin Liston (Version: 2)
13 comment(s)

I'm getting a lot of emails asking about articles that ultimately reference this upcoming talk: "BEAST: Surprising crypto attack against HTTPS" (

I don't have any extra details.  Anything that I write now will be unnecessary speculation.  It sounds like it will be interesting; their presentation last year on Padded Oracle Attacks (the crypto Oracle, not the database) certainly was.

" that may describe the attack.  This attack requires that the attacker be able to sniff the traffic and run code on the victims machine to inject the chosen-plaintext into the stream. 

My recommendation is still to wait until we see the details before formulating a response, but sight-unseen the following steps couldn't hurt:

  1. Users: Don't bank using someone else's wifi.
  2. Browser Authors: Update to support TLS 1.2
  3. Servers Admins: Configure to support TLS 1.2
Keywords: TLS
13 comment(s)


Juliano Rizzo presents this friday the attack and the tool "Beast" at Ekoparty.

More info here:
Yes, those would be the articles. I'd like to postpone any response until we see the actual presentation.

an older paper that appears to describe this type of attack. I am with Kevin on withholding further discussion until seeing the attack/paper:
So, I just know my boss is going to ask,. "If SSL is dead and TLS is broken, how do we secure our web sites?" I don't have a good answer for him. Thoughts?
@RobM's boss: we recommend waiting until Friday when there are details to analyze. But if you insist on doing something now, upgrading your servers to support TLS 1.2 couldn't hurt.
Anyone have a link on how to upgrade Apache 2.2 to support TLS 1.2? The apache 2.2 reference here: doesn't seem to provide a 1.2 protocol configuration option.
I once attended a demonstration of Zcaler (hosted web filtering service) where they bragged about "breaking SSL on the fly" to monitor for data leak. Am I missing something here? Should the padlock icon be replaced by someone laughing?
Last comment should say "ZScaler" of course
@confused. They are using HTTP inspect, where you are presented a certificate from the device intercepting your request, with some information from the original cert.

Essentially they do a MITM on your SSL traffic. So not breaking the protocol at all.
openssl doesn't support TLS 1.1 or 1.2. Apache doesn't support TLS 1.1 or 1.2.. the browsers don't TLs 1.1 or 1.2.

This problem has been kept really quiet ... I wonder why – Implement TLS 1.1 (RFC 4346) – Implement support for TLS 1.2 (RFC 5246)

Diary Archives