|Professional Services||Second Signal||Presentations||Andrew's Blog||Support|
Rather than repeat what everyone else is writing about POODLE today, I want to give Domino server administrators a few quick items as it relates to them.
In Brief -- and based on what I've been able to quickly learn:
IS Domino affected?
Yes. All Domino servers that are accepting direct HTTPS connections are impacted. THIS MEANS ALL TRAVELER SERVERS AS WELL.
What is the risk to my server or data?
The most immediate risk is access to user data and user impersonation. POODLE is the type of attack we call "Man in the Middle". This means someone who can get access to the TCPIP traffic between a user's browser and the server can access or alter that content. This is not a "take down the server" attack - not directly. However, in theory the credentials of someone with access to other resources on the server that could take it down is possible. For example, if your credentials were captured and an attacker was able to use them or take over your session and you had access to the web administration client, the attacker could use that tool to do all kinds of bad things.
How big is this risk?
Big enough. Although the hole has been there for all of the last 18 years, the published methods for exploiting that hole are now readily available and quickly making their way into scripted tools that any idiot with a laptop at the coffee shop can use to attack your users.
Is there a Domino server setting to fix this?
At this time, -NO-. There does not appear to be a simple domino INI setting to fix this. We hope that there will be one published, maybe something left over from debugging code that is not published which turns off SSL 3.0 but at this time, SSL 3.0 is always enabled on the Domino HTTPS stack.
What Can I do?
There are configurations being posted for Apache and for IBM HTTP SERVER (IHS). Either of these can be configured in a "Reverse Proxy" configuration. Russ Maher has a great two-blog article on how to set up IHS in Domino 9 and turn on TLS which will resolve much of the issues. As additional configuration steps come out today which tell you how to turn off SSL 3.0 in IHS you should use those in combination with Russ's article and that should do the trick.
What do I do in the mean time?
Setting up a reverse proxy isn't super easy. If you are worried about exploits in the mean time, you'll have to council your users NOT to use the tools from coffee shops, wifi hotspots, hotel networks, or other places where they do not personally own the connection to the ISP. You may also want to turn off Traveler. I know that's a huge deal -- but you asked.
Where can I get more detailed information on Poodle?
Bill Malchisky has put together a page on it, and if I know Bill, he'll be diligent about keeping it up to date. Otherwise, just do a web search. It's all over the news.
Please wait while your document is saved.