Second, please please please restrict your Microsoft Federation settings. Especially in big Windows shops, where the only Macs might be a handful in the graphic design department, it’s easy for non-standard machines to fall through the cracks when it comes to patching and managing software. What can you do? First, make sure that if your organization uses Macs, that they are held to the same standard for vulnerability management. You should see a prompt appear on the target machine, and the URL should open in a new browser window! If you go to the Skype for Business 2016 Mac client download page you see that they recommend using the Lync 2011 client when connecting to Lync Server 2010. With that being said, if they don’t want to fix it, Microsoft should stop recommending it and remove it from their downloads page.
#Microsoft lync for mac 2013 install#
Plus, it’s the Mac client, so the install base is likely on the smaller side. Lync: Mac 2011 is an aging client, with two product replacements out for it already (Skype for Business, and the new Microsoft Teams). I’m not completely surprised by their decision not to fix the problem. The Microsoft Security Advisory can be found here: September, 11 2018 – Microsoft discloses existence of vulnerability CVE-2018-8474.July 2018 – Microsoft has decided they won’t be publishing fix after all.May 2018 – Microsoft decides to fix it after all.April 2018 – File with MITRE for CVE, MITRE contacts Microsoft.March 2018 – Microsoft decides not to fix.November 2017 – Microsoft has been able to replicate issue.I reported this to Microsoft in July 2017 and the MSRC opened a ticket. Disclosure Timeline and Microsoft’s Response
0 kommentar(er)
