{"id":5906,"date":"2018-05-09T11:13:44","date_gmt":"2018-05-09T16:13:44","guid":{"rendered":"https:\/\/www.tecklyfe.com\/?p=5906"},"modified":"2018-05-10T15:37:55","modified_gmt":"2018-05-10T20:37:55","slug":"how-to-fix-authentication-error-function-not-supported-credssp-error-rdp","status":"publish","type":"post","link":"https:\/\/www.tecklyfe.com\/how-to-fix-authentication-error-function-not-supported-credssp-error-rdp\/","title":{"rendered":"How to Fix Authentication Error Function Not Supported CredSSP Error RDP"},"content":{"rendered":"

\"\"<\/p>\n

In March 2018, Microsoft released the CredSSP Updates for CVE-2018-0886, which is a vulnerability that could allow for remote code execution in unpatched versions of CredSSP. It would allow an attacker to relay user credentials to execute code on a target system. According to this Microsoft KB Article<\/a>, they initially released an update in March. Then in April they released an update that would provide a more detailed error message while using the Remote Desktop Client (RDP). Then, finally, in the May 2018 Patch Tuesday, they just released an update that changed the default setting from Vulnerable to Mitigated which means that any client application that uses CredSSP will not be able to fall back to insecure versions. In other words, if you have a workstation that received the May update but a server that hasn’t received the CredSSP update, the workstation will receive the error message above when trying to RDP to that server.<\/p>\n

Recommended Fix for Authentication Error Function Not Supported CredSSP Error<\/h2>\n

Obviously to reduce the risk of the vulnerability, the recommended solution is to patch all of the servers that are missing the update. Unfortunately, this update does require a reboot.<\/p>\n

For more information, see the Microsoft article CredSSP updates for CVE-2018-0886<\/a>.<\/p>\n

Group Policy Temporary Workaround Fix for Authentication Error Function Not Supported CredSSP Error<\/h2>\n

If you cannot update your server right away, then the temporary workaround is to change a Group Policy. This is not recommended<\/strong> for a permanent solution since it means that the vulnerability could still exist on the servers.<\/p>\n

Note:<\/strong> Ensure that you update the Group Policy Central Store (Or if not using a Central Store, use a device with the patch applied when editing Group Policy) with the latest CredSSP.admx and CredSSP.adml. These files will contain the latest copy of the edit configuration settings for these settings. If you do not have a patched server with access to Group Policy, then you won’t see the necessary settings because you’ll have an older version of CredSSP.admx and CredSSP.adml. You can try this copy of the ADMX and ADML files that I pulled from a patched Windows 2012 R2 server from my OneDrive<\/a>.<\/p>\n