Exploited
Advisory Published
Updated

CVE-2017-0199: Microsoft Office and WordPad Remote Code Execution Vulnerability

First published: Wed Apr 12 2017(Updated: )

Microsoft Office 2007 SP3, Microsoft Office 2010 SP2, Microsoft Office 2013 SP1, Microsoft Office 2016, Microsoft Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, Windows 8.1 allow remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office/WordPad Remote Code Execution Vulnerability w/Windows API."

Credit: secure@microsoft.com secure@microsoft.com

Affected SoftwareAffected VersionHow to fix
Microsoft Office and WordPad
Microsoft Office=2007-sp3
Microsoft Office=2010-sp2
Microsoft Office=2013-sp1
Microsoft Office=2016
Microsoft Windows 7=sp1
Microsoft Windows Server 2008 Itanium=sp2
Microsoft Windows Server 2008 Itanium=r2-sp1
Microsoft Windows Server 2012 x64
Microsoft Windows Vista=sp2
Philips IntelliSpace Portal=7.0
Philips IntelliSpace Portal=8.0
Microsoft Office=2016
Microsoft Windows 7=sp1
Microsoft Windows Server 2008 Itanium=sp2
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-2017-0199?

    CVE-2017-0199 has a critical severity rating due to its ability to allow remote code execution through specially crafted documents.

  • How do I fix CVE-2017-0199?

    To fix CVE-2017-0199, users should apply the latest security updates provided by Microsoft for the affected versions of Office and Windows.

  • What software is affected by CVE-2017-0199?

    CVE-2017-0199 affects multiple versions of Microsoft Office, including Office 2007 SP3, 2010 SP2, 2013 SP1, and 2016, along with various Windows operating systems.

  • How does CVE-2017-0199 exploit work?

    CVE-2017-0199 exploits vulnerabilities in Microsoft Office and WordPad to execute arbitrary code via crafted documents, allowing remote attackers to gain control.

  • Is there a workaround for CVE-2017-0199?

    While the best solution is to apply patches, users can mitigate the risk of CVE-2017-0199 by avoiding opening untrusted documents or enabling Protected View in Office.

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