CVE-2016-3396: Critical severity Microsoft Live Meeting vulnerability

Published Oct 14, 2016
·
Updated

Graphics Device Interface (aka GDI or GDI+) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold, 1511, and 1607; Office 2007 SP3; Office 2010 SP2; Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; and Live Meeting 2007 Console allows remote attackers to execute arbitrary code via a crafted embedded font, aka "GDI+ Remote Code Execution Vulnerability."

Affected Software

19 affected components
Microsoft Live Meeting=2007
Microsoft Lync=2010
Microsoft Lync=2010
Microsoft Lync=2013-sp1
Microsoft Office=2007-sp3
Microsoft Office=2010-sp2
Microsoft Skype for Business=2016
Microsoft Word Viewer
Microsoft Windows 10
Microsoft Windows 10=1511
Microsoft Windows 10=1607
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Vista=sp2

Event History

Oct 14, 2016
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-3396?

CVE-2016-3396 is classified as a critical vulnerability that can allow remote code execution.

2

How do I fix CVE-2016-3396?

To fix CVE-2016-3396, install the security updates provided by Microsoft for the affected software versions.

3

What software is affected by CVE-2016-3396?

CVE-2016-3396 affects multiple versions of Microsoft Windows, Microsoft Office, and Skype for Business, among others.

4

Can CVE-2016-3396 be exploited remotely?

Yes, CVE-2016-3396 can be exploited remotely, allowing an attacker to execute arbitrary code.

5

Is there a workaround for CVE-2016-3396?

There are no known workarounds for CVE-2016-3396; updating to the latest patches is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203