this could be due to credssp encryption oracle remediation

Patched via wsus and aditionally checked via online search. But this is such so deep nonsense.Īll of my server are up to date. In fact, they released iterative patches to clients as a warning over both months! Microsoft released the updates on the server side two months ago with plenty of explanations about what was coming. Personally I'm angling to have all my clients ditch RDP and switch to something more secure. Always a silver lining somewhere if you look for it. Having ranted, it's also noted that RDP attacks have been ramping up a lot lately, so at least Microsoft is trying to address vulnerabilities. If I had to read through every bulletin on every patch and update released by Microsoft I'd never get any work done. For more information, see CredSSP updates for CVE-2018-0886.Īnother thing about Microsoft Updates - they often link back to link back links, weaving a web of confusion that I simply do not have time to try to decipher. May 8, 2018-KB4103727 (OS Build 16299.431) Īddresses an issue that may cause an error when connecting to a Remote Desktop server. I also experienced this problem from my now-patched Windows 10 圆4 workstation. Microsoft even ended up pulling the patch with no real explanation, and issued a new patch that did nothing to fix the damage caused. Even after removing the update, when some users log out the system blue screens. I still have clients getting a BSOD from KB4088875. In the last few months there have been a number of Microsoft Update 'surprise!' days.

This could be due to credssp encryption oracle remediation