Threat Signal Report
Out of Band Advisory (CVE-2020-1425) and (CVE-2020-1457) - Microsoft Windows Codecs Library Remote Code Execution Vulnerability
Today, Microsoft released two out of band advisories for CVE-2020-1425 and CVE-2020-1457. Both CVEs contain a remote code execution vulnerability in the Microsoft Windows Codecs Library, specifically in a how it handles objects in memory. CVE-2020-1425 allows an attacker to potentially obtain information about a victim's system for further compromise and is rated CRITICAL. CVE-2020-1457 allows an attacker to execute arbitrary code via a specially crafted file and is rated IMPORTANT.
What are the vulnerabilities specifically?
According to Microsoft they are:
A remote code execution vulnerability exists in the way that Microsoft Windows Codecs Library handles objects in memory. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user's system. Exploitation of the vulnerability requires that a program process a specially crafted image file.
A remote code execution vulnerability exists in the way that Microsoft Windows Codecs Library handles objects in memory. An attacker who successfully exploited the vulnerability could execute arbitrary code.
Exploitation of the vulnerability requires that a program process a specially crafted image file.
Is there a patch available?
Microsoft states that all platforms affected running the Windows Media Codec will be automatically updated by the Microsoft Store. Customers also have the option of checking the Microsoft Store manually for updates. Further information can be found here.
What platforms are affected?
Windows 10, Windows Server 2019, and Windows Server version 1709/1803/1903/2004 (server core installation) are affected.
Are there reports of active exploitation in the wild?
No. According to the advisory, Microsoft has not observed in the wild attacks.
Any suggestions or mitigation?
Microsoft has not provided any mitigation or workarounds for these two out of band advisories.
What is the status of AV and IPS coverage?
IPS coverage is currently being investigated for feasibility. We will update this post once relevant information is available.
AV coverage is not feasible for this event.
FortiGuard Labs recommends that all AV and IPS definitions are kept up to date on a continual basis, and that organizations maintain a proactive patching routine when vendor updates are available. If it is deemed that patching is not feasible, it is recommended that a risk assessment is conducted to determine additional mitigation safeguards within an environment.
Traffic Light Protocol
|Color||When Should it Be used?||How may it be shared?|
TLP: REDNot for disclosure, restricted to participants only.
|Sources may use TLP:RED when information cannot be effectively acted upon by additional parties, and could lead to impacts on a party's privacy, reputation, or operations if misused.||Recipients may not share TLP:RED information with any parties outside of the specific exchange, meeting, or conversation in which it was originally disclosed. In the context of a meeting, for example, TLP:RED information is limited to those present at the meeting. In most circumstances, TLP:RED should be exchanged verbally or in person.|
TLP: AMBERLimited disclosure, restricted to participants’ organizations.
|Sources may use TLP:AMBER when information requires support to be effectively acted upon, yet carries risks to privacy, reputation, or operations if shared outside of the organizations involved.||Recipients may only share TLP:AMBER information with members of their own organization, and with clients or customers who need to know the information to protect themselves or prevent further harm. Sources are at liberty to specify additional intended limits of the sharing: these must be adhered to.|
TLP: GREENLimited disclosure, restricted to the community.
|Sources may use TLP:GREEN when information is useful for the awareness of all participating organizations as well as with peers within the broader community or sector.||Recipients may share TLP:GREEN information with peers and partner organizations within their sector or community, but not via publicly accessible channels. Information in this category can be circulated widely within a particular community. TLP:GREEN information may not be released outside of the community.|
TLP: WHITEDisclosure is not limited.
|Sources may use TLP:WHITE when information carries minimal or no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release.||Subject to standard copyright rules, TLP:WHITE information may be distributed without restriction.|