CVE-2018-0802
Exploited in the wild. In CISA KEV since 2021‑11‑03. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record- Check whether your business devices use Microsoft Office Equation Editor (often via Microsoft Word/Office 2007/2010/2013/2016, Microsoft Office Compatibility Pack, or Equation Editor) and confirm the installed version/service pack.
- Identify whether you have one of the affected configurations listed for Microsoft Office/Equation Editor (for example: Office 2016 Click-to-Run C2R, or the listed Word service packs).
- Update Microsoft Office/Equation Editor immediately using Microsoft’s guidance for CVE-2018-0802.
- Verify after updating that the device has the vendor-provided security fix for CVE-2018-0802 (by checking the installed Office build/patch level against the vendor instructions).
What it is
From the CVE record
Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allow a remote code execution vulnerability due to the way objects are handled in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE is unique from CVE-2018-0797 and CVE-2018-0812.
In plain language
Written by AI from the recordThis is a serious Office Equation Editor bug that can let attackers run code, and it has been used in real ransomware attacks—if you use affected Microsoft Office versions, you should act now to install the vendor fixes.
CVE-2018-0802 is a remote code execution vulnerability in the Microsoft Equation Editor used by Microsoft Office (including Office 2007/2010/2013/2016, Office Compatibility Pack, and Equation Editor); attackers can trigger memory corruption by sending a specially crafted Office file to a user, which is then handled by the Equation Editor.
If you're affected
- Full system compromise
- Ransomware infection risk
- Data theft from workstation
- Business disruption via outage
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2021-11-03.
US federal agencies must remediate by 2022-05-03.
Known use in ransomware campaigns.
Apply updates per vendor instructions.
- Public exploits
6 sources with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
93% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 129 days before any public exploit.
- EPSS band changehigh → criticalepss band change
- EPSS band changecritical → high
- EPSS band changecritical → highepss band change
- OpenVAS check added
- Public exploit / PoCsource: other
- Patch availablerecord updated
Affected products
- Microsoft Office 2010 Service Pack 2Consumer Software / productivity
- Microsoft Word 2010 Service Pack 2Consumer Software / productivity
- Microsoft Word 2007 Service Pack 3Consumer Software / productivity
- Microsoft Word 2013 Service Pack 1Consumer Software / productivity
- Microsoft Office Compatibility Pack Service Pack 3Consumer Software / productivity
- Microsoft Word 2013 RT Service Pack 1Consumer Software / productivity
- Microsoft Word 2016Consumer Software / productivity
- Microsoft Office 2016 Click-to-Run (C2R)Operating Systems / windows
And 6 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored 7.8 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1190Exploit Public-Facing Applicationhigh confidence
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
References in the record
- securityfocus.com/bid/102347&
- securitytracker.com/id/1040153&
- 0patch.blogspot.com/2018/01/the-bug-that-killed-equation-editor-how.html&
And 12 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Microsoft Corp, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI