POODLE TLS - The POODLE Strikes Back - change your settings now....
Go scan your servers at SSL Labs.
Anyway, provided you are using 9.0.1 FP IF1 (the TLS fix that IBM provided a while back) the apparent Domino fix is to disable AES and 3DES ciphers and run with only RC4:
With those changes you go from an "F" to a "B" on SSL Labs. Here is the server with AES and/or 3DES enabled:
Here is a Domino server with just RC4 enabled:
Oh, and F5's are also at risk.....
If you're on anything less than 9 then you don't get TLS so you're not affected by this.....oh, the irony. Still it would be very beneficial to IBM's public perception to get TLS 1.2 and better ciphers into Domino ASAP. Fixing this stuff once a decade is not cutting it. As you can see above RC4 is not to hot these days.
As Adam Langley puts it:
This seems like a good moment to reiterate that everything less than TLS 1.2 with an AEAD cipher suite is cryptographically broken
So, IBM, the ball is in your court again.......
I will be updating my free proxy soon, but that is not affected by this issue, it still gets a "B".
Discussion for this entry is now closed.
Comments (10)
We needed to disable SSL3 so went to IHS on our 9.0.1 FP2 IF1 Traveler server. That is now showing as an F (his server is vulnerable to the POODLE attack against TLS servers. Patching required. Grade set to F.) even though SSL is completely disabled in Domino as IHS is doing HTTPS/TLS. Thoughts? Back to Domino doing SSL in the shot term but still be vulnerable as SSL3 is still enabled in Domino.
Has anybody with Windows Domino & IHS tried this workaround setting to enforce "strict CBC padding" yet?
{ http://www-01.ibm.com/support/docview.wss?uid=swg21692502 }
Workarounds and Mitigations
For all versions and releases of Apache based IBM HTTP server, IBM recommends enabling strict CBC padding enforcement. Add the following directive to the httpd.conf file to disable SSLv3 and SSLv2 for each context that contains "SSLEnable":
# Enable strict CBC padding
SSLAttributeSet 471 1
On Domino 9/IHS, I previously disabled all ciphers other than RC4 which brought the SSL Labs score up to B, noting the weak cipher. I've now re-enabled all ciphers, disabling the RC4 ciphers, and added SSLAttrubuteSet 471 1. Server is now back to A-. Need to do some further testing etc but looking OK so far.
>>If you're on anything less than 9 then you don't get TLS so you're not affected by this...
Not true. 8.5.3 FP6 with IF4 (shows as "HF1024" in "show server") enables the same TLS 1.0 stack including the new POODLE 2.0 bug.