CVE-2017-11882: Microsoft Office Memory Corruption Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1, and Microsoft Office 2016 allow an attacker to run arbitrary code in the context of the current user by failing to properly handle objects in memory, aka “Microsoft Office Memory Corruption Vulnerability”. This CVE ID is unique from CVE-2017-11884.
Description quoted from the CVE record (assigned by microsoft, published 2017-11-15).
Weakness: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
How it can be exploited
Exploitable with local access with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2021-11-03
- US federal deadline
- 2022-05-03
- Ransomware use
- Yes
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 Exploit-DB entry, 39 code repositories and 12 research write-ups naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 68 references on Exploit Observer
Live scores
- EPSS
- 0.999
very likely to be attacked soon - VEDAS
- 0.984
strong exploit evidence - On CISA KEV
- Yes, since 2021-11-03
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Microsoft Corporation Microsoft Office | version Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1, Microsoft Office 2016 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
CISA required action: Apply updates per vendor instructions.
Vendor guidance:
How to detect it
This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.
Advisories on this CVE
References
Exploit code
- 43163 (exploit, x_refsource_EXPLOIT-DB)
Technical analysis and advisories
- VU#421280 (third-party-advisory, x_refsource_CERT-VN)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-11882 (government-resource)
Other references
- https://github.com/embedi/CVE-2017-11882 (x_refsource_MISC)
- https://github.com/unamer/CVE-2017-11882 (x_refsource_MISC)
- http://reversingminds-blog.logdown.com/posts/3907313-fileless-attack-in-word-without-macros-cve-2017-11882 (x_refsource_MISC)
- https://github.com/rxwx/CVE-2017-11882 (x_refsource_MISC)
- 101757 (vdb-entry, x_refsource_BID)
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-11882 (x_refsource_CONFIRM)
- https://researchcenter.paloaltonetworks.com/2017/12/unit42-analysis-of-cve-2017-11882-exploit-in-the-wild/ (x_refsource_MISC)
- 1039783 (vdb-entry, x_refsource_SECTRACK)
- https://0patch.blogspot.com/2017/11/did-microsoft-just-manually-patch-their.html (x_refsource_MISC)
- https://0patch.blogspot.com/2017/11/official-patch-for-cve-2017-11882-meets.html (x_refsource_MISC)
- https://github.com/0x09AL/CVE-2017-11882-metasploit (x_refsource_MISC)
- https://web.archive.org/web/20181104111128/https://embedi.com/blog/skeleton-closet-ms-office-vulnerability-you-didnt-know-about/ (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners