CVE DatabaseCVE-2018-0802
한국어 권고문 →
CVE-2018-08027.8/HIGHCISA KEVCWE-787CWE-787

Microsoft Office Equation Editor Memory Corruption Remote Code Execution Vulnerability (CVE-2018-0802) Technical Analysis and Hardening Guide

⚡ Jump to Patch
Affected Vendors
microsoft
Affected Components
office, equation_editor
Published Date
2018-01-10
CVSS v3.1
7.8
HIGH
EPSS (30d)
93.3%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Equation Editor (EQNEDT32.EXE) included in Microsoft Office 2007, 2010, 2013, and 2016

Impact

Remote attackers can execute arbitrary code with the privileges of the logged-in user by enticing them to open a specially crafted document containing malicious OLE objects

Mitigation

Apply the official Microsoft security patches immediately, or disable the Equation Editor component via registry modification

Affected Products & Version Scope

Microsoft Office 2007, 2010, 2013, and 2016 containing the legacy Equation Editor (EQNEDT32.EXE) component

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

Administrators should deploy the latest security updates provided by Microsoft. In enterprise environments, you can force Windows Update to scan and install Office updates using the following PowerShell script:

powershell
# Force Windows Update to search and install missing Microsoft Office security updates
$UpdateSession = New-Object -ComObject 'Microsoft.Update.Session'
$UpdateSearcher = $UpdateSession.CreateUpdateSearcher()
$SearchResult = $UpdateSearcher.Search("IsInstalled=0 and Type='Software' and Title like '%Office%'")

if ($SearchResult.Updates.Count -gt 0) {
    Write-Host 'Missing Office security updates found. Initiating installation...'
    # Automation logic for patch deployment
} else {
    Write-Host 'All Office security patches are up to date.'
}

2. Temporary Workaround & Hardening Configuration

If patching cannot be immediately applied, disable the Equation Editor component entirely by setting the COM Compatibility Killbit in the Windows Registry.

powershell
# Disable Equation Editor (EQNEDT32.EXE) via Registry Killbit
$regPath = 'HKLM:\SOFTWARE\Microsoft\Office\Common\COM Compatibility\{0002CE02-0000-0000-C000-000000000046}'
if (-not (Test-Path $regPath)) {
    New-Item -Path $regPath -Force | Out-Null
}
New-ItemProperty -Path $regPath -Name 'Compatibility Flags' -Value 0x00000400 -PropertyType DWord -Force

# Apply the same mitigation for 32-bit Office on 64-bit Windows (Wow6432Node)
$wowRegPath = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Office\Common\COM Compatibility\{0002CE02-0000-0000-C000-000000000046}'
if (-not (Test-Path $wowRegPath)) {
    New-Item -Path $wowRegPath -Force | Out-Null
}
New-ItemProperty -Path $wowRegPath -Name 'Compatibility Flags' -Value 0x00000400 -PropertyType DWord -Force

3. Log Audit & IoC Verification Commands

Run the following script to audit endpoints for the presence of the vulnerable EQNEDT32.EXE binary and verify its version.

powershell
# Audit system for the presence of EQNEDT32.EXE
$eqPaths = @(
    'C:\Program Files\Common Files\microsoft shared\EQUATION\EQNEDT32.EXE',
    'C:\Program Files (x86)\Common Files\microsoft shared\EQUATION\EQNEDT32.EXE'
)

foreach ($path in $eqPaths) {
    if (Test-Path $path) {
        $versionInfo = (Get-Item $path).VersionInfo
        Write-Warning "Vulnerable component detected: $path (Version: $($versionInfo.FileVersion))"
    } else {
        Write-Host "Secure: Component not found at $path"
    }
}
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Due to active exploitation in the wild, immediately apply the official Microsoft security updates or implement the registry workaround to disable Equation Editor.

Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot

Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.

100% MITRE ATT&CK Detection · 1-Click Rollback

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability (CVE-2018-0802) is an out-of-bounds write (CWE-787) memory corruption vulnerability in the legacy Equation Editor (EQNEDT32.EXE) component of Microsoft Office. The root cause lies in the improper validation of input data length when the application processes OLE (Object Linking and Embedding) objects in memory. This allows an attacker to overflow the stack or heap buffers by supplying malformed data structures.

2. Exploitation Mechanics & Attack Scenario

An attacker exploits this vulnerability by embedding a maliciously crafted Equation object inside an Office document (such as an RTF or DOCX file). When a user opens the document, Microsoft Office automatically spawns the EQNEDT32.EXE process to render the embedded equation. Due to the lack of bounds checking, the malicious payload overwrites critical memory structures, hijacking the instruction pointer to execute arbitrary shellcode. This bypasses modern exploit mitigations because the legacy EQNEDT32.EXE binary was not compiled with ASLR/DEP protections in older versions.

3. Infrastructure & Business Impact

CVE-2018-0802 is a highly critical vulnerability listed in the CISA KEV catalog, with an EPSS score exceeding 0.93, indicating extremely high active exploitation in the wild. Successful exploitation grants the attacker full control over the victim's endpoint, serving as an initial access vector for ransomware deployment, lateral movement, and sensitive data exfiltration.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2018-0802)

FAQ

Q1. How critical is CVE-2018-0802 and is it actively exploited in the wild?

CVE-2018-0802 is rated CVSS 7.8 (HIGH) with a 30-day EPSS exploitation probability of 93.3%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2018-0802?

Primary impacted vendors include microsoft across office, equation_editor. Scope summary: Microsoft Office 2007, 2010, 2013, and 2016 containing the legacy Equation Editor (EQNEDT32.EXE) component

Q3. What temporary mitigations or workarounds exist for CVE-2018-0802 before patching?

[Mitigation] Apply the official Microsoft security patches immediately, or disable the Equation Editor component via registry modification Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2018-0802

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (microsoft)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2018-0802 Microsoft Office Equation Editor Memory Corruption Remote Code Execution Vulnerability (CVE-2018-0802) Technical Analysis and Hardening Guide (CVSS 7.8) - Patch & Workaround | CVE Pulse