A remote code execution vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory, aka 'Microsoft Office Memory Corruption Vulnerability'.
No fixed version listed yet.Check the vendor advisory. References ↓
Microsoft · Microsoft Office
A memory handling flaw in Microsoft Office software allows remote code execution because the software fails to properly handle objects in memory. An attacker can exploit it to execute code.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 8 days after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+8 days
Affected versions and fixes
as published in the CVE recordMicrosoft Microsoft Office
Affected: 2019 for 32-bit editions · 2019 for 64-bit editions · 2016 (32-bit edition) · 2016 (64-bit edition) · 2010 Service Pack 2 (32-bit editions) · 2010 Service Pack 2 (64-bit editions) · 2013 RT Service Pack 1 · 2013 Service Pack 1 (32-bit editions) · 2013 Service Pack 1 (64-bit editions)
Microsoft Office 365 ProPlus
Affected: 32-bit Systems · 64-bit Systems
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.