dbcve.org
OfficeApplication · Microsoft

CVE-2015-6093

HIGH · 9.3 CVSS v2.0 Published 2015-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office 2016, Word Automation Services on SharePoint Server 2010 SP2 and 2013 SP1, Office Web Apps 2010 SP2, and Office Web Apps Server 2013 SP1 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

A memory corruption vulnerability in Microsoft Office allows remote attackers to execute arbitrary code via specially crafted Office documents. The vulnerability affects Office 2007 SP3 through Office 2016 and related SharePoint/Office Web Apps components, enabling code execution when users open maliciously constructed files.

MitigationDeploy Microsoft security updates (MS15-116 or subsequent cumulative updates) to all affected Office installations and SharePoint servers, or implement application whitelisting and disable opening of untrusted Office documents.

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:= 2007= 2010= 2013= 2016
Office Web AppsApplication
Affected:= 2010
Office Web Apps ServerApplication
Affected:= 2013
Sharepoint ServerApplication
Affected:= 2010= 2013

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
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 Office version
    Open Word (winword.exe), go to File > Account > About Word, or run 'winword.exe /?' from Command Prompt to see version information. Alternatively, check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\(version)\Common\InstallRoot for version details.
    Affected if The installed version corresponds to Office 2007, 2010, 2013, or 2016 (all service pack levels within these versions are affected)
  2. Check for Microsoft SharePoint Server installation
    Check installed programs list in Control Panel, or query registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions for version information.
    Affected if SharePoint Server 2010 or 2013 is installed
  3. Check for Office Web Apps or Office Web Apps Server
    Check installed programs list, or query IIS Manager for installed web applications. Check registry or program files for Office Web Apps components.
    Affected if Office Web Apps 2010 or Office Web Apps Server 2013 is installed
  4. Verify default document handling is enabled
    Confirm that Office applications are configured to open documents normally (check that file associations for .docx, .xlsx, .pptx are not blocked or set to read-only). This is the default configuration for most installations.
    Affected if Office applications can open and process Office document files, which is the standard default behavior

A user is affected if they have Office 2007/2010/2013/2016, SharePoint Server 2010/2013, or Office Web Apps 2010/2013 installed AND the system is configured to open Office documents (the default state).

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy Microsoft security updates (MS15-116 or subsequent cumulative updates) to all affected Office installations and SharePoint servers, or implement application whitelisting and disable opening of untrusted Office documents.

Recommended fix Moderate confidence

Microsoft Security Update MS15-116 (November 2015)

  1. Locate the appropriate Microsoft security update for this vulnerability (MS15-116) from docs.microsoft.com or the Microsoft Security Response Center
  2. For Office 2007: Apply KB3102890
  3. For Office 2010: Apply KB3102893
  4. For Office 2013: Apply KB3102907
  5. For Office 2016: Apply KB3102906
  6. For SharePoint Server 2010: Apply KB3102894
  7. For SharePoint Server 2013: Apply KB3102920
  8. For Office Web Apps 2010: Apply KB3102897
Caveat Standard Microsoft patches rarely introduce breaking changes; test in non-production environment before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Office Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6093 — 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-2015-6093 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