F5 DROWNing, not waving, in crypto fail

If you're an F5 BIG-IP sysadmin, get patching: there's a bug in the company's RSA implementation that can give an attacker access to encrypted messages. As the CVE assignment stated: “a virtual server configured with a Client SSL profile may be vulnerable to an Adaptive Chosen Ciphertext attack (AKA Bleichenbacher attack) …

[John Smith 19]

But note "Significantly more difficult" does not mean impossible

Especially with state actors.

[Sir Runcible Spoon]

Eh?

"(Decrypting RSA with Obsolete and Weakened Encryption)"

Surely that would be DROWE then?

[NoneTheFewer]

Re: Eh?

DR SAOWE!

[Deltics]

Re: Eh?

Encryption -> "En..." -> N

As in "Dee Are Oh Double-You En"

Unless you spell out DROWN as "Duh Ruh O Wuh Nuh". :)

[Sir Runcible Spoon]

Re: Eh?

I see what you are saying Deltics (and I understand that some acronyms borrow letters from a word subsequent to the first) but it still doesn't make any sense.

Also, it was just a joke :P

[teknopaul]

Did I miss something, seems like an F5 misconfigured to permit downgrade attacks is vulnerable to downgrade attacks.

[EnviableOne]

Nah just the BIG-IP with big Intelectual Property holes in it again

[Anonymous Coward]

Cloudflare's statement is incorrect

The RSA key is NEVER in danger of being exposed here. The easiest fix is to use ECDHE:DHE instead of RSA for key exchanges. “DEFAULT:!RSA” or “ECDHE:DHE” makes this a non-issue.