First published: Thu May 21 2020(Updated: )
A memory corruption vulnerability exists when Windows Media Foundation improperly handles objects in memory, aka 'Media Foundation Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-1028, CVE-2020-1126, CVE-2020-1150.
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
Windows 10 | ||
Windows 10 | ||
Windows 10 | =1607 | |
Windows 10 | =1607 | |
Windows 10 | =1709 | |
Windows 10 | =1803 | |
Windows 10 | =1809 | |
Windows 10 | =1903 | |
Windows 10 | =1909 | |
Microsoft Windows | ||
Microsoft Windows | ||
Microsoft Windows RT | ||
Microsoft Windows Server | =r2 | |
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2016 | =1803 | |
Microsoft Windows Server 2016 | =1903 | |
Microsoft Windows Server 2016 | =1909 | |
Microsoft Windows Server 2019 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-1136 has a severity rating of important, indicating it may lead to vulnerabilities like memory corruption.
To fix CVE-2020-1136, you should apply the latest updates available for your affected Microsoft Windows operating system.
CVE-2020-1136 affects various versions of Microsoft Windows, including Windows 10, Windows 8.1, and Windows Server versions.
The impact of CVE-2020-1136 includes potential memory corruption which may allow for remote code execution.
There is no specific workaround for CVE-2020-1136; applying security patches is the recommended action.