CVE-2016-3282: Buffer Overflow

Published Jul 13, 2016
·
Updated

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Word 2016, Word for Mac 2011, Word 2016 for Mac, Office Compatibility Pack SP3, Word Viewer, Word Automation Services on SharePoint Server 2010 SP2, Word Automation Services on SharePoint Server 2013 SP1, SharePoint Server 2016, Office Web Apps 2010 SP2, Office Web Apps Server 2013 SP1, and Office Online Server allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."

Affected Software

16 affected components
Microsoft Office=2010-sp2
Microsoft Office Compatibility Pack=sp3
Microsoft Office Online Server
Microsoft Office Web Apps=2010-sp2
Microsoft Office Web Apps Server=2013-sp1
Microsoft SharePoint Server=2010-sp2
Microsoft SharePoint Server=2013-sp1
Microsoft SharePoint Server=2016
Microsoft Word=2007-sp3
Microsoft Word=2010-sp2
Microsoft Word=2013-sp1
Microsoft Word=2016
Microsoft Word for Mac=2011
Microsoft Word for Mac=2016
Microsoft Word Rt=2013-sp1
Microsoft Word Viewer

Event History

Jul 13, 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-3282?

CVE-2016-3282 is classified as a critical vulnerability that allows for remote code execution.

2

How do I fix CVE-2016-3282?

To fix CVE-2016-3282, update your affected Microsoft Office products to the latest version available.

3

What operating systems are affected by CVE-2016-3282?

CVE-2016-3282 affects multiple versions of Microsoft Office and is present in both Windows and Mac operating systems.

4

What types of attacks can exploit CVE-2016-3282?

CVE-2016-3282 can be exploited through maliciously crafted Word documents opened by vulnerable applications.

5

Is CVE-2016-3282 still a risk if my software is up to date?

If your software is fully updated to the latest security patches, the risk from CVE-2016-3282 should be mitigated.

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