#VU5059 Memory corruption in Microsoft products - CVE-2016-0145

Vulnerability identifier: #VU5059

Vulnerability risk: High

CVSSv4.0: 7 [CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/U:Amber]

CVE-ID: CVE-2016-0145

CWE-ID: CWE-119

Exploitation vector: Network

Exploit availability: Yes

Vulnerable software:
Windows
Operating systems & Components / Operating system
Windows Server
Operating systems & Components / Operating system
Microsoft Live Meeting
Client/Desktop applications / Messaging software
Skype for Business
Client/Desktop applications / Messaging software
Lync Attendee
Client/Desktop applications / Messaging software
Microsoft Lync
Client/Desktop applications / Messaging software
Microsoft Office
Client/Desktop applications / Office applications
Microsoft .NET Framework
Server applications / Frameworks for developing and running applications

Vendor: Microsoft

Description
The vulnerability allows a remote attacker to execute arbitrary code on the target system.

The weakness exists due to boundary error when handling of malicious embedded fonts. A remote attacker can create a specially crafted content, trick the victim into opening it, trigger memory corruption and execute arbitrary code.

Successful exploitation of the vulnerability results in arbitrary code execution on the vulnerable system.

Mitigation
Install update from vendor's website.

Vulnerable software versions

Windows: Vista, 7, 8.1 RT - 8.1, 10

Windows Server: 2008 R2 - 2008, 2012 R2 - 2012

Microsoft Live Meeting: 2007 Console

Microsoft Office: 2007, 2010

Microsoft .NET Framework: 3.0, 3.5 - 3.5.1

Skype for Business: 2016

Lync Attendee: 2010

Microsoft Lync: 2013

---

External links
https://technet.microsoft.com/en-us/library/security/ms16-039

---

Q & A

Can this vulnerability be exploited remotely?

Yes. This vulnerability can be exploited by a remote non-authenticated attacker via the Internet.

Is there known malware, which exploits this vulnerability?

No. We are not aware of malware exploiting this vulnerability. However, proof of concept for this vulnerability is available.