90 Remote Code Execution Vulnerabilities in May “Update Tuesday”

    "World. Work. May ”is not only about pleasant work in the country, but also about installing updates, all the more so since this month office software manufacturers did a great job and closed a total of 162 vulnerabilities, of which 90 allow arbitrary code to be executed on the system.


    Immediately 2 vulnerabilities that can be exploited remotely were fixed in Windows. We announced the most dangerous one last night - the vulnerability CVE-2019-070 in the Remote Desktop service allows the exploit owner to execute code with SYSTEM privileges. We recommend updating all terminal servers accessible from the outside as quickly as possible. Also, do not forget to update the DHCP server from the CVE-2019-0725 vulnerability , since it can also be operated remotely.

    Two other vulnerabilities deserve attention: CVE-2019-0863 and CVE-2019-0903. The first allows you to increase privileges in the system, and the exploit is already walking on the network. The second is located in the graphical component of Windows GDI and can be operated through different vectors - both through the browser and using a file sent, for example, by mail.

    May brought us four more hardware vulnerabilities of speculative execution in Intel processors , one of which already has its own website with the beautiful name Zombieload . Recommendations for countering this type of vulnerability are standard : upgrade and disable Hyper-Threading in the processor. At the same time, you can check the speculative execution settings using this Powershell script .

    In addition, Microsoft and Adobe eliminated another 87 vulnerabilities that could allow arbitrary code to be executed on the system:







    In the end, we want to recall two more serious vulnerabilities in the Cisco 1001-X routers called Thrangrycat . They allow not only increasing privileges in the router, but also gaining a foothold there, essentially installing a bootkit in the firmware of the router , which will bypass the check of the Trust Anchor module responsible for the trusted boot mechanism.

    Also popular now: