First published: Tue Apr 09 2019(Updated: )
A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka 'Windows VBScript Engine Remote Code Execution Vulnerability'.
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
Windows 10 | ||
Windows 10 | =1607 | |
Windows 10 | =1703 | |
Windows 10 | =1709 | |
Windows 10 | =1803 | |
Windows 10 | =1809 | |
Microsoft Windows 7 | =sp1 | |
Microsoft Windows | ||
Microsoft Windows RT | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =r2-sp1 | |
Microsoft Windows Server | =r2-sp1 | |
Microsoft Windows Server | ||
Microsoft Windows Server | =r2 | |
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2016 | =1709 | |
Microsoft Windows Server 2016 | =1803 | |
Microsoft Windows Server 2019 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-0842 has a critical severity rating due to its potential for remote code execution.
To fix CVE-2019-0842, apply the latest security updates provided by Microsoft for your affected Windows version.
CVE-2019-0842 affects various versions of Windows including Windows 7, Windows 8.1, Windows 10, and several Windows Server editions.
If exploited, CVE-2019-0842 allows attackers to execute arbitrary code on the affected system, potentially leading to system compromise.
While the best mitigation for CVE-2019-0842 is to apply security updates, disabling VBScript in Internet Explorer can serve as a temporary workaround.