July 9, 2019
Microsoft Windows is prone to a remote code-execution vulnerability. An attacker can leverage this issue to execute arbitrary code in the context of the currently logged-in user. Failed exploit attempts will likely result in denial of service conditions.
- Microsoft Windows 10 Version 1709 for ARM64-based Systems
- Microsoft Windows 10 Version 1803 for 32-bit Systems
- Microsoft Windows 10 Version 1803 for ARM64-based Systems
- Microsoft Windows 10 Version 1803 for x64-based Systems
- Microsoft Windows 10 Version 1809 for 32-bit Systems
- Microsoft Windows 10 Version 1809 for ARM64-based Systems
- Microsoft Windows 10 Version 1809 for x64-based Systems
- Microsoft Windows 10 Version 1903 for 32-bit Systems
- Microsoft Windows 10 Version 1903 for ARM64-based Systems
- Microsoft Windows 10 Version 1903 for x64-based Systems
- Microsoft Windows 10 version 1709 for 32-bit Systems
- Microsoft Windows 10 version 1709 for x64-based Systems
- Microsoft Windows Server 1803
- Microsoft Windows Server 1903
- Microsoft Windows Server 2019
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, block access at the network perimeter to computers hosting the vulnerable operating system.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity such as unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.
Communicate sensitive information through secure means.
Implement multiple layers of encryption and authentication to help mitigate against exposure from this and other latent vulnerabilities.
Updates are available. Please see the references or vendor advisory for more information.
Mateusz Jurczyk of Google Project Zero
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.