Encryption Oracle Remediation
Correction d'oracle de chiffrement
Explanation
Encryption Oracle Remediation
This policy setting applies to applications using the CredSSP component (for example: Remote Desktop Connection).
Some versions of the CredSSP protocol are vulnerable to an encryption oracle attack against the client. This policy controls compatibility with vulnerable clients and servers. This policy allows you to set the level of protection desired for the encryption oracle vulnerability.
If you enable this policy setting, CredSSP version support will be selected based on the following options:
Force Updated Clients: Client applications which use CredSSP will not be able to fall back to the insecure versions and services using CredSSP will not accept unpatched clients. Note: this setting should not be deployed until all remote hosts support the newest version.
Mitigated: Client applications which use CredSSP will not be able to fall back to the insecure version but services using CredSSP will accept unpatched clients. See the link below for important information about the risk posed by remaining unpatched clients.
Vulnerable: Client applications which use CredSSP will expose the remote servers to attacks by supporting fall back to the insecure versions and services using CredSSP will accept unpatched clients.
For more information about the vulnerability and servicing requirements for protection, see https://go.microsoft.com/fwlink/?linkid=866660
Correction d'oracle de chiffrement
Ce paramètre de stratégie s'applique aux applications qui utilisent le composant CredSSP (par exemple : Connexion Bureau à distance).
Certaines versions du protocole CredSSP sont vulnérables à une attaque de l'oracle de chiffrement à l'encontre du client. Cette stratégie contrôle la compatibilité avec des clients et serveurs vulnérables. Cette stratégie vous permet de définir le niveau de protection souhaité pour la vulnérabilité de l'oracle de chiffrement.
Si vous activez ce paramètre de stratégie, la prise en charge de la version CredSSP est sélectionnée en fonction des options suivantes :
Forcer les clients mis à jour : les applications clientes qui utilisent CredSSP ne peuvent pas avoir recours aux versions non sécurisées et les services qui utilisent CredSSP n'acceptent pas les clients non corrigés. Remarque : ce paramètre ne doit pas être déployé tant que tous les hôtes distants ne prennent pas en charge la dernière version.
Atténué : les applications clientes qui utilisent CredSSP ne peuvent pas avoir recours à la version non sécurisée, mais les services qui utilisent CredSSP acceptent les clients non corrigés. Consultez le lien ci-dessous pour obtenir des informations importantes sur le risque représenté par des clients non corrigés restants.
Vulnérable : les applications clientes qui utilisent CredSSP exposent les serveurs distants aux attaques en prenant en charge le recours à des versions non sécurisées et les services qui utilisent CredSSP acceptent les clients non corrigés.
Pour plus d'informations sur la vulnérabilité et les conditions de maintenance pour la protection, voir https://go.microsoft.com/fwlink/?linkid=866660
Use cases
Sets how tolerant CredSSP, used among others by Remote Desktop, is toward unpatched clients and servers affected by the CVE-2018-0886 encryption oracle flaw. Three levels: “Force updated clients” (0), “Mitigated” (1, the default since the May 8, 2018 update) and “Vulnerable” (2).
The trap is compatibility: by default a patched client cannot connect to an unpatched server, and “Force updated clients” additionally makes servers reject unpatched clients, so deploy it only once every remote host is updated. Choosing “Vulnerable” restores the connection but exposes the remote servers, and any change requires a restart.
Microsoft source: CredSSP updates for CVE-2018-0886
Registry
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Enable
# Enable: CredSsp/AllowEncryptionOracle
$k = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Protection Level
# Possible options:
# Force Updated Clients = 0
# Mitigated = 1
# Vulnerable = 2
Set-ItemProperty -Path $k -Name 'AllowEncryptionOracle' -Value 1 -Type DWordDisable
# Disable: CredSsp/AllowEncryptionOracle
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": CredSsp/AllowEncryptionOracle
$k = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters'
Remove-ItemProperty -Path $k -Name 'AllowEncryptionOracle' -ErrorAction SilentlyContinueOptions (1)
| Label | Control | Registry value | REG type | Constraints / details | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Protection Level:Niveau de protection :AllowEncryptionOracleDrop | Drop-down listenum | AllowEncryptionOracle | REG_DWORD | Default choice (UI): #1
|