{"id":10663,"date":"2014-10-20T09:10:00","date_gmt":"2014-10-20T08:10:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=10663"},"modified":"2014-11-20T08:54:06","modified_gmt":"2014-11-20T07:54:06","slug":"microsoft-iis-disable-sslv3-protocol-poodle-vulnerability","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/microsoft-iis-disable-sslv3-protocol-poodle-vulnerability\/","title":{"rendered":"Microsoft IIS disable SSLv3 protocol for POODLE vulnerability"},"content":{"rendered":"

\"disablessl3iis01\"<\/p>\n

The POODLE vulnerability is an attack on the SSL 3.0 protocol and it's a protocol flaw<\/strong> not an implementation issue. Read the Google release post<\/a>.<\/p>\n

Every implementation of SSL 3.0 suffers from it. Security experts are recommending administrators to disable SSL 3.0<\/strong> on their servers and use TLS 1.1 or 1.2.<\/p>\n

<\/p>\n

 <\/p>\n

Check SSL 3.0 usage<\/h2>\n

To check if your server uses SSL v3, go to GeoTrust SSL Toolbox<\/a> website and type the URL of the server you want to check and click Check<\/strong> button.<\/p>\n

\"disablessl3iis02\"<\/p>\n

If the result shows SSLv3 is enabled<\/strong>, the server may be affected by\u00a0POODLE vulnerability.<\/p>\n

 <\/p>\n

Manual fix<\/h2>\n

Run Regedit<\/strong> as Administrator and navigate to:<\/p>\n

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\Schannel\\Protocols\\<\/pre>\n
\"disablessl3iis03\"<\/p>\n
Right click Protocols<\/strong> and select New > Key<\/strong> option.<\/p>\n
\"disablessl3iis04\"<\/p>\n
Name the new key as SSL 3.0<\/strong>.<\/p>\n
\"disablessl3iis05\"<\/p>\n
Now right click SSL 3.0<\/strong> and create a new key named Client<\/strong>.<\/p>\n
\"disablessl3iis06\"<\/p>\n
Again, right click SSL 3.0<\/strong> and create the key Server<\/strong>.<\/p>\n
\"disablessl3iis07\"<\/p>\n
Right click Client<\/strong> and select\u00a0 New > DWORD (32bit) Value<\/strong> option.<\/p>\n
\"disablessl3iis08\"<\/p>\n
Name the DWORD as DisabledByDefault<\/strong>. Double click the DWORD and type 1<\/strong> as Value data<\/strong> then click OK<\/strong> to confirm.<\/p>\n
\"disablessl3iis09\"<\/p>\n
The DWORD Value Data<\/strong> set to 1.<\/p>\n
\"disablessl3iis10\"<\/p>\n
Repeat same procedure for Server<\/strong> and assign Enabled<\/strong> as a DWORD name. Leave default Value Data<\/strong> set to 0<\/strong>.<\/p>\n
\"disablessl3iis11\"<\/p>\n
Restart the server<\/strong> to complete the procedure.<\/p>\n
 <\/p>\n
Quick fix<\/h2>\n
Log into the server with Local Administrator permissions<\/strong> account.<\/p>\n
Download disable_ssl3.zip<\/a> and extract the .reg file<\/strong>.<\/p>\n
\"disablessl3iis12\"<\/p>\n
Double click the .reg file<\/strong> and click Yes<\/strong> to confirm.<\/p>\n
\"disablessl3iis13\"<\/p>\n
The system confirms the keys added to the Registry.<\/p>\n
\"disablessl3iis14\"<\/p>\n
The Registry keys added.<\/p>\n
\"disablessl3iis15\"<\/p>\n
No patches are available so far since it's a protocol flaw<\/strong> and not an implementation issue.<\/p>\n
\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"
The POODLE vulnerability is an attack on the SSL 3.0 protocol and it's a protocol flaw not an implementation issue. Read the Google release post. Every implementation of SSL 3.0 suffers from it. Security experts are recommending administrators to disable SSL 3.0 on their servers and use TLS 1.1 or 1.2.<\/p>\n","protected":false},"author":3,"featured_media":10648,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[913,1065],"tags":[1087,1083,680],"class_list":["post-10663","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-active-directory-en","category-microsoft-en","tag-iis-en-en-en","tag-poodle-en","tag-ssl-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/10663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=10663"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/10663\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/10648"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=10663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=10663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=10663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}