dbcve.org
Sharepoint FoundationApplication · Microsoft

CVE-2013-3847

HIGH · 9.3 CVSS v2.0 Published 2013-09-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 Word Automation Services in SharePoint Server 2010 SP1, Word Web App 2010 SP1 in Office Web Apps 2010, Word 2003 SP3, Word 2007 SP3, Word 2010 SP1, Office Compatibility Pack SP3, and Word Viewer allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted Office document, aka "Word Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3848, CVE-2013-3849, and CVE-2013-3858.

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 exists in Microsoft Word and related Office products when parsing specially crafted Office documents. Attackers can exploit this to execute arbitrary code or cause denial of service by enticing users to open malicious .doc files. The vulnerability affects Word Automation Services in SharePoint Server 2010, Word Web App 2010, Word 2003/2007/2010, Office Compatibility Pack, and Word Viewer.

MitigationApply the relevant Microsoft security patches (MS13-079) to all affected Word installations and SharePoint/Office Web Apps servers. Until patches are applied, instruct users not to open Office documents from untrusted 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
Sharepoint FoundationApplication
Affected:= 2010
Sharepoint Portal ServerApplication
Affected:= 2003
Sharepoint ServerApplication
Affected:= 2010
Sharepoint ServicesApplication
Affected:= 2.0= 3.0
Office Web AppsApplication
Affected:= 2010
Office Compatibility PackApplication
Affected:all versions
WordApplication
Affected:= 2003= 2007= 2010
Word ViewerApplication
Affected:all versions

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. Check installed Microsoft Word version
    Open Word, go to File > Help, or run 'winword.exe /?' from command line, or check Add/Remove Programs for Microsoft Office installation
    Affected if Version is 2003, 2007, or 2010 (any build within these versions)
  2. Check Word Viewer installation
    Look for 'Microsoft Office Word Viewer' in Add/Remove Programs or check Program Files for WordView folder
    Affected if Word Viewer is installed (any version)
  3. Check Office Compatibility Pack version
    Look for 'Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint' in Add/Remove Programs
    Affected if Compatibility Pack is installed (any version)
  4. Check SharePoint Server 2010 version
    On SharePoint server, open Central Administration > Help > About, or run 'Get-SPFarm | Select-Object BuildVersion' in SharePoint Management Shell
    Affected if Build version matches SharePoint Foundation/Server 2010 (14.x)
  5. Check Office Web Apps 2010 installation
    Check installed programs for 'Microsoft Office Web Apps' or run 'Get-OfficeWebAppsMachine' in SharePoint Management Shell on the server
    Affected if Office Web Apps 2010 is installed

Your environment is affected if any of the following are present: Word 2003, 2007, or 2010; Word Viewer (any version); Office Compatibility Pack; SharePoint Foundation/Server 2010; Office Web Apps 2010.

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

Apply the relevant Microsoft security patches (MS13-079) to all affected Word installations and SharePoint/Office Web Apps servers. Until patches are applied, instruct users not to open Office documents from untrusted sources.

Recommended fix High confidence

Microsoft Security Bulletin MS13-086 (October 2013)

  1. Install Microsoft Security Bulletin MS13-086 from https://technet.microsoft.com/en-us/security/bulletin/ms13-086
  2. For Word 2003: Apply the update for Word 2003 SP3 (KB2827320)
  3. For Word 2007: Apply the update for Word 2007 SP3 (KB2827324)
  4. For Word 2010: Apply the update for Word 2010 SP1 or SP2 (KB2826023)
  5. For Office Compatibility Pack: Apply the update (KB2827326)
  6. For SharePoint Server 2010 with Word Automation Services: Apply update (KB2827327)
  7. For Office Web Apps 2010: Apply update (KB2827217)
  8. For Word Viewer: Update to the latest version with the security patch
Caveat May require restart of services; ensure compatibility testing with existing Office workflows before broad deployment

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

Fix this in Sharepoint Foundation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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