5 posts
December 2014 Patch Tuesday
It is December, time for our last Patch Tuesday of the year. Microsoft is publishing seven bulletins this month bringing the total count for the year to 85. Compared to 2013 with 106 and 2011 with 100 bulletins, 85 bulletins is not particularly high.
Poodle Bites TLS
There’s a new SSL/TLS problem being announced today and it’s likely to affect some of the most popular web sites in the world, owing largely to the popularity of F5 load balancers and the fact that these devices are impacted. There are other devices known to be affected, and it’s possible that the same flaw is present in some SSL/TLS stacks. We will learn more in the following days.
If you want to stop reading here, take these steps: 1) check your web site using the SSL Labs test; 2) if vulnerable, apply the patch provided by your vendor. As problems go, this one should be easy to fix.
SSLv3 and POODLE attacks – Update
Update:
When POODLE was disclosed, we added detection capabilities to Qualys VM immediately. We have now integrated a POODLE filter into our Certificate Dashboard (similar to the HeartBleed filter) that will help organizations to look at their exposure through POODLE in a natural, real-time way. The following selections in the Filters menu quickly identify which hosts are affected by POODLE:
- Poodle – All: lists all certificates that have been used on systems that were (or still are) vulnerable to POODLE.
- Poodle – Active: lists all certificates currently in use on systems that are still vulnerable to POODLE.
Take a look at the Certificates tab under Assets in Qualys VM.
Original: Late on Patch Tuesday three researchers from Google announced the POODLE (Padding Oracle On Downgraded Legacy Encryption) vulnerability CVE-2014-3566 in SSLv3. It is an attack against the protocol itself, meaning that all implementations of SSL are vulnerable, differently from HeartBleed which was a flaw in OpenSSL. Similarly to HeartBleed it is an information disclosure, as a successful attack would be able to steal a session cookie from you, but again differently from HeartBleed it is much harder to exploit in that it requires a MITM (Man in The Middle) position and code on the client to open numerous SSL attempts against a vulnerable server. A successful attack will reveal information about the particular session from that endpoint, again different from Heartbleed where one could gain information about other users.
SSL 3 is dead, killed by the POODLE attack
The POODLE Attack (CVE-2014-3566)
Update (8 Dec 2014): Some TLS implementations are also vulnerable to the POODLE attack. More information in this follow-up blog post.
After more than a week of persistent rumours, yesterday (Oct 14) we finally learned about the new SSL 3 vulnerability everyone was afraid of. The so-called POODLE attack is a problem in the CBC encryption scheme as implemented in the SSL 3 protocol. (Other protocols are not vulnerable because this area had been strengthened in TLS 1.0.) Conceptually, the vulnerability is very similar to the 2011 BEAST exploit. In order to successfully exploit POODLE the attacker must be able to inject malicious JavaScript into the victim’s browser and also be able to observe and manipulate encrypted network traffic on the wire. As far as MITM attacks go, this one is complicated, but easier to execute than BEAST because it doesn’t require any special browser plugins. If you care to learn the details, you can find them in the short paper or in Adam Langley’s blog post.