CWE
20
Advisory Published
Updated

CVE-2016-3301: Input Validation

First published: Tue Aug 09 2016(Updated: )

The Windows font library 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 "Windows Graphics Component RCE Vulnerability."

Credit: secure@microsoft.com

Affected SoftwareAffected VersionHow to fix
Microsoft Live Meeting=2007
Microsoft Lync Server=2010
Microsoft Lync Server=2010
Microsoft Lync Server=2013-sp1
Microsoft Office=2007-sp3
Microsoft Office=2010-sp2
Microsoft Skype for Business=2016
Microsoft Office Word Viewer
Microsoft Windows 10
Microsoft Windows 10=1511
Microsoft Windows 10=1607
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT
Microsoft Windows Server=sp2
Microsoft Windows Server=r2-sp1
Microsoft Windows Server
Microsoft Windows Server=r2
Microsoft Windows Vista=sp2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2016-3301?

    CVE-2016-3301 is rated as important due to potential exploitation leading to code execution.

  • How do I fix CVE-2016-3301?

    To fix CVE-2016-3301, ensure that all impacted Microsoft software is updated with the latest security patches.

  • Which versions of Windows are affected by CVE-2016-3301?

    CVE-2016-3301 affects versions including Windows Vista, Windows 7, Windows 8.1, Windows 10, and various Windows Server editions.

  • What types of applications are vulnerable to CVE-2016-3301?

    CVE-2016-3301 impacts multiple Microsoft applications, including Office 2007, Office 2010, Skype for Business, and Lync.

  • Is there a workaround for CVE-2016-3301?

    There are no specific workarounds for CVE-2016-3301, so applying the security update is recommended to mitigate the risk.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203