How do I patch CVE­-2014­-3566 on a Windows Server 2012 system running IIS?

Is there a patch in Windows Update, or do I have to do a registry change to disable SSL 3.0?

  • 1
    There is a Microsoft Fix it 50495 on the MS KB page you linked to.
    – MattBianco
    Commented Oct 16, 2014 at 7:59
  • 3
    I tried running Fix it 50495 on Windows 2008, and it failed with error "This Microsoft Fix it does not apply to your operating system or application version." Oh well.
    – Josh
    Commented Oct 20, 2014 at 15:34

8 Answers 8


There is no "patch". It's a vulnerability in the protocol, not a bug in the implementation.

In Windows Server 2003 to 2012 R2 the SSL / TLS protocols are controlled by flags in the registry set at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols.

To disable SSLv3, which the POODLE vulnerability is concerned with, create a subkey at the above location (if it's not already present) named SSL 3.0 and, under that, a subkey named Server (if it's not already present). At this location (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\SSL 3.0\Server) create a DWORD value named Enabled and leave it set at 0.

Disabling SSL 2.0, which you should also be doing, is done the same way, except that you'll be using a key named SSL 2.0 in the above registry path.

I haven't tested all versions, but I think it's probably safe to assume that a reboot is necessary for this change to take effect.

  • 3
    reboot not necessary on Windows Server 2012 at least. you can verify before and after at poodlebleed.com by entering your URL and 443 for SSL port
    – Simon
    Commented Oct 31, 2014 at 0:49
  • Thanks, Do you know if I should disable PCT as well since its allegedly disabled by default and yet not disabled in this way ? Commented Nov 4, 2014 at 11:52
  • @Simon, is there something else you have to do to get the changes to take effect? I just made the registry updates on a Server 2012 machine, but it's still getting reported that SSL3 is enabled. Commented Dec 18, 2014 at 17:37
  • I don't believe so. I'm assuming you're using iis and my Apache and you checked usjng that website. And you're sure you have the exact right registry key?
    – Simon
    Commented Dec 18, 2014 at 17:39
  • * NOT apache (I don't know where 'my Apache' came from!)
    – Simon
    Commented Dec 20, 2014 at 1:08

Just for ease of installation I derived this "disable ssl 2 and 3.reg" file from Evan's answer above:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server]

Powershell to disable SSL2 and SSL3:

2..3 | %{ New-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL $_.0\Server" -Name Enabled -PropertyType "DWORD" -Value 0 -Force }
  • Unfortunately the above only works if the registry subkeys are already present. Would be nice to see PS that can create them if not exists or update them if they do.
    – Jaans
    Commented Oct 19, 2014 at 23:50
  • Are you sure? Mine creates them for me. It might differ on lower versions of Powershell and Windows (I'm using v2 on Server 2008 R2) Commented Oct 19, 2014 at 23:51
  • 2
    Yup... see screenshot uploaded to: i.imgur.com/rctFH4D.png Using PS 3.0 and WSMan 3.0.
    – Jaans
    Commented Oct 19, 2014 at 23:54

There is a free utility from Nartac that you can use to disable the protocols.



Here's a PowerShell that will test for the presence of the registry keys, create them if needed, and then enter the necessary values to disable SSL 2.0 and SSL 3.0

$regPath1 = 'HKLM:SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\SSL 2.0'
$regPath2 = 'HKLM:SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\SSL 2.0\Server'
$regPath3 = 'HKLM:SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\SSL 3.0'
$regPath4 = 'HKLM:SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel\Protocols\SSL 3.0\Server'

If(!(Test-Path -Path $regPath1))
New-Item -Path $regPath1 -Force

If(!(Test-Path $regPath2))
New-Item -Path $regPath2 -Force
   New-ItemProperty -Path $regPath2 -Name DisabledByDefault -PropertyType DWORD -Value "1" -Force
   New-ItemProperty -Path $regPath2 -Name Enabled -PropertyType DWORD -Value "0" -Force 

If(!(Test-Path $regPath3))
New-Item -Path $regPath3 -Force

If(!(Test-Path $regPath4))
New-Item -Path $regPath4 -Force
   New-ItemProperty -Path $regPath4 -Name DisabledByDefault -PropertyType DWORD -Value "1" -Force
   New-ItemProperty -Path $regPath4 -Name Enabled -PropertyType DWORD -Value "0" -Force

This can be deployed using SCCM or command line - just be sure to run the SCCM job or command line as Administrator. Some websites with the registry information indicate that a reboot is required after the registry keys are created and/or modified.


Or grab a copy of IISCrypto and click the best practices button, then uncheck SSL 3.0 and then apply, then reboot


You don't have to disable SSL3. You can enable SSL3 and have POODLE mitigated.

# Copy and paste this in PowerShell then restart your server
$cipherSuitesOrder = @(
$cipherSuitesAsString = [string]::join(',', $cipherSuitesOrder)
New-ItemProperty -path 'HKLM:\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002' \
-name 'Functions' -value $cipherSuitesAsString -PropertyType 'String' -Force | Out-Null

With these settings you would still have IE6 support (with SSLv3 using RC4) and have a more than acceptable configuration security wise. Only IE6 and really old client would be using SSLv3 or RC4 ciphers.


There's a good PowerShell script that helps with IIS 7.5 & 8 configuration:

This PowerShell script setups your Microsoft Internet Information Server 7.5 and 8.0 (IIS) to support TLS 1.1 and TLS 1.2 protocol with Forward secrecy. Additionally it increases security of your SSL connections by disabling insecure SSL2 and SSL3 and and all insecure and weak ciphers that a browser may fall-back, too. This script implements the current best practice rules.


  • Hmm, not sure why this was down voted. I used that utility myself and it works perfectly. Commented May 28, 2015 at 7:18
  • This looks good but at least one guy has had problems after running it - don't know if it's isolated seen other people say it's great.
    – Mark
    Commented Oct 8, 2015 at 22:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .