CVE-2017-11882
Memory Safety in Microsoft Office 2007 … 2016
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2017-11882 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Microsoft Office. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1, and Microsoft Office 2016 are affected by CVE-2017-11882, a memory corruption vulnerability tracked under CWE-119. The flaw stems from improper handling of objects in memory and carries a CVSS 3.1 score of 7.8, reflecting local attack vector, low complexity, no required privileges, and required user interaction.
An attacker can exploit the issue by supplying a specially crafted document that triggers the memory corruption when opened in an affected Office application. Successful exploitation grants the ability to execute arbitrary code in the context of the current user, potentially leading to full confidentiality, integrity, and availability impacts on the affected system.
Public references describe both an official Microsoft patch and third-party micropatches such as those from 0patch, along with demonstrations of fileless attack techniques in Word that avoid macros. These sources indicate that applying the vendor update or equivalent micropatch addresses the memory handling defect.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2017-3478
Vulnerability Data
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…
more
handle objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11884.
- CWE(s)
- KEV Date Added
- 03 November 2021
Related Threats
Threat-Actor AttributionAI
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, testing including code scans and penetration tests, developer training) that reach buffer management and can stop many buffer overruns from reaching production, but leaves a bounded remainder (e.g. flaws in non-software components, incomplete enforcement of guidelines, or post-deployment changes)
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
A.8.27 mandates security-by-design principles (e.g. least privilege, fail securely, distrust external input, hardening) plus design reviews that can catch and stop buffer-boundary errors before they reach code, but this is only one minority slice of CWE-119's broad surface (language-specific flaws, unsafe library use, compiler/runtime mitigations, and post-deployment instances remain outside its direct scope).
Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.
Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-119, a class-level weakness. Rules are authored against its narrower children: CWE-823.