Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Microsoft Office Equation Editor Memory Corruption RCE

IdentifiersCVE-2018-0802CWE-119

CVE-2018-0802 is a remote code execution vulnerability in the legacy Microsoft Office Equation Editor component (EQNEDT32.EXE) affecting Microsoft Office 2007, 2010, 2013, and 2016. According to the provided content, the flaw exists because Equation Editor improperly handles objects in memory, resulting in memory corruption during parsing/processing of malicious embedded content. Attackers commonly weaponize crafted Office documents, including RTF, Word, Excel, or XLAM/OLE-bearing files, so that opening the document invokes Equation Editor and triggers shellcode execution. The vulnerability is distinct from CVE-2018-0797 and CVE-2018-0812.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote code execution on the victim system in the security context of the user who opens the malicious Office document. In observed campaigns cited in the content, exploitation was used to launch shellcode, download HTA or PowerShell stages, execute malware loaders, and install RATs/backdoors such as XWorm, VBCloud, PowerShower, and other payloads. This can lead to full system compromise, malware installation, persistence, credential theft, reconnaissance, lateral movement, and data exfiltration, depending on follow-on tooling and user privileges.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by blocking or quarantining untrusted Office attachments, especially documents containing embedded OLE objects or Equation Editor content; restrict execution paths commonly used in observed exploit chains such as mshta.exe and PowerShell; disable or isolate risky attachment types such as XLAM where operationally feasible; and use email/web filtering and endpoint controls to detect malicious Office documents and follow-on payload retrieval. User-facing mitigations include preventing opening of unsolicited attachments and enforcing Protected View and related document hardening controls, though bypasses may exist in broader attack chains.

Remediation

Patch, then assume compromise.

Apply Microsoft security updates for the affected Microsoft Office versions referenced in the content (Office 2007, 2010, 2013, and 2016) that address CVE-2018-0802. Prioritize patching or retiring systems that still expose the legacy Equation Editor attack surface. Where possible, upgrade to supported Office builds and remove or disable vulnerable legacy components no longer required by business workflows.
PUBLIC EXPLOITS

Exploits

3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 3 / 3 TOTALView more in app
CVE-2018-0802_POCMaturityPoCVerified exploit

This repository is a proof-of-concept (PoC) exploit for CVE-2018-0802, a vulnerability in Microsoft Office's Equation Editor that allows for arbitrary code execution via a crafted RTF file. The repository contains three files: a README with usage instructions, a sample malicious RTF file ('cve-2018-0802.rtf'), and a Python script ('cve-2018-0802_poc.py') that generates malicious RTF files. The Python script takes an executable command (such as 'calc.exe' or a remote executable path) and outputs an RTF file that, when opened in a vulnerable version of Microsoft Word, will execute the specified command. The exploit leverages the embedding of an OLE object with a crafted Equation.3 object to trigger the vulnerability. The main attack vector is through a malicious file delivered to the victim, and the payload is customizable to execute arbitrary commands. The exploit is a PoC and does not include advanced features such as evasion or persistence.

zldww2011Disclosed Jan 11, 2018pythonfile
CVE-2018-0802MaturityPoCVerified exploit

This repository provides a proof-of-concept exploit for CVE-2018-0802 (and optionally CVE-2017-11882), both critical vulnerabilities in the Microsoft Office Equation Editor. The main exploit script, 'packager_exec_CVE-2018-0802.py', generates a malicious RTF file that embeds a user-supplied executable using a Packager OLE object. When the RTF is opened in a vulnerable version of Microsoft Office, the exploit drops the embedded executable to the %TMP% directory and executes it via a WinExec call, achieving arbitrary code execution. The script supports an option to exploit both CVE-2018-0802 and CVE-2017-11882 in a single document. The repository also includes a sample malicious RTF ('example/example.rtf') that launches calc.exe, YARA rules for detection of the exploit, and a utility script ('yara/strip_keycodes.py') for removing obfuscating keycodes from RTF files. The exploit is a POC and requires the attacker to supply the payload executable. The attack vector is via malicious file delivery (RTF), and the main fingerprintable endpoint is the dropped file in the %TMP% directory.

rxwxDisclosed Jan 11, 2018pythonyarafile
RTF_11882_0802MaturityPoCVerified exploit

This repository contains a Python proof-of-concept exploit for the Microsoft Office Equation Editor vulnerabilities CVE-2017-11882 and CVE-2018-0802. The main file, RTF_11882_0802.py, is a command-line tool that generates a malicious RTF file. The user specifies a command to execute on the target system and the output file name for the crafted RTF. Optionally, a template RTF can be provided. The exploit works by embedding a specially crafted OLE object into the RTF, which triggers the vulnerability in the Equation Editor component when the file is opened in a vulnerable version of Microsoft Office on Windows. The exploit does not contain any hardcoded payload; instead, it allows the user to specify any command, making it a flexible proof-of-concept. The repository also includes a README with usage instructions and references to research and advisories. No network endpoints or external IPs/domains are present; the attack vector is via a malicious file delivered to the victim.

RidterDisclosed Jan 12, 2018pythonfile
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationOfficeapplication
Microsoft CorporationOffice Compatibility Packapplication
Microsoft CorporationWordapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence22

Every observed campaign linking this CVE to a named adversary.

Associated malware18

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity25

Community discussion across Reddit, Mastodon, and other social sources.