dbcve.org
OfficeApplication · Microsoft

CVE-2016-3282

HIGH · 7.8 CVSS v3.0 Published 2016-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory corruption vulnerability in Microsoft Word and related Office products that allows remote code execution via specially crafted Office documents. The vulnerability affects multiple versions of Word (2007-2016), Office, Word Viewer, SharePoint Word Automation Services, and Office Web Apps/Online Server.

MitigationApply Microsoft security updates (MS16-099) and avoid opening untrusted or unexpected Office documents from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OfficeApplication
Affected:= 2010
Office Compatibility PackApplication
Affected:all versions
Office Online ServerApplication
Affected:all versions
Office Web AppsApplication
Affected:= 2010
Office Web Apps ServerApplication
Affected:= 2013
Sharepoint ServerApplication
Affected:= 2010= 2013= 2016
WordApplication
Affected:= 2007= 2010= 2013= 2016
Word For MacApplication
Affected:= 2011= 2016

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Microsoft Word version
    Open Word, go to File > Account > About Word, or run 'winword.exe /?' from command prompt, or check Programs and Features in Control Panel
    Affected if Version is 2007, 2010, 2013, or 2016 (any build within these versions)
  2. Identify installed Microsoft Office version
    Open any Office app, go to File > Account > About, or check Programs and Features for Microsoft Office installations
    Affected if Version is 2010 (any build)
  3. Check for Microsoft Office Compatibility Pack
    Open Programs and Features and look for 'Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint File Formats'
    Affected if Compatibility Pack is installed (all versions are affected)
  4. Identify SharePoint Server version
    Check SharePoint Central Administration > System Settings > Manage servers in this farm, or check Programs and Features for Microsoft SharePoint Server
    Affected if Version is 2010, 2013, or 2016
  5. Identify Office Web Apps Server version
    Check Programs and Features or the farm configuration via SharePoint Management Shell
    Affected if Version is 2013 (any build)
  6. Confirm attack vector presence
    Review email filtering and document handling policies - determine if users can open unsolicited Office attachments from external sources
    Affected if Users routinely open Office documents from untrusted or unknown sources without sanitization

You are affected if any installed product matches the affected versions listed (Office 2010, Word 2007/2010/2013/2016, Word for Mac 2011/2016, SharePoint 2010/2013/2016, Office Web Apps 2010/2013, or Office Online Server any version) AND users can open unsolicited Office documents.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates (MS16-099) and avoid opening untrusted or unexpected Office documents from unknown sources.

Fix this in Office Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-3282 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data