CVE-2017-11882: Microsoft Office Memory Corruption
Microsoft Office · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 99.9%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2017-11882 explained
CVE-2017-11882 is a memory corruption vulnerability in Microsoft Office caused by improper handling of objects in memory. It lets an attacker run arbitrary code in the context of the current user. CISA lists it as known exploited, including use in ransomware campaigns, which makes patching a priority.
Impact
An attacker who succeeds can run arbitrary code with the rights of the logged-in user, with high impact on confidentiality, integrity and availability. User interaction is required, and no privileges are needed. CISA rates the technical impact as total and automatable as no. Attackers are known to exploit this vulnerability, and CISA reports known ransomware use. Users with administrative rights increase the potential damage.
Who is affected
The CVE record lists Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1 and Microsoft Office 2016 as affected. The CVE record names no fixed version. Check the Microsoft security advisory for the updates that address this vulnerability for each Office edition.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Corporation Microsoft OfficeAffectedFixed in
- Microsoft Office 2007 Service Pack 3
- Microsoft Office 2010 Service Pack 2
- Microsoft Office 2013 Service Pack 1
- Microsoft Office 2016
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Corporation Microsoft Office |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for CVE-2017-11882 to all affected Office installations, as CISA's required action directs.
- Identify every system running Microsoft Office 2007, 2010, 2013 or 2016 and confirm the update is installed.
- Have users work without administrative rights to limit what code running in their context can do.
- Warn users about opening documents from untrusted or unexpected sources.
- Check systems for signs of compromise, given known exploitation and ransomware use.
The CVE record names no fixed version. Follow the Microsoft security advisory, which identifies the updates for each affected Office edition, and apply them as CISA requires. Until updates are confirmed installed, limit user privileges, treat documents from untrusted sources with caution and monitor affected systems for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Questions about CVE-2017-11882
- Is CVE-2017-11882 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and reports known ransomware use. US federal agencies had to remediate it by 2022-05-03.
- Does an attacker need an account on the system?
- No privileges are required, but user interaction is. Code runs in the context of the current user, so limiting user rights reduces the impact.
- Which versions fix the issue?
- The CVE record names no fixed version. Use the Microsoft security advisory to find the applicable updates and apply them per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.