CVE DatabaseCVE-2014-1761
한국어 권고문 →
CVE-2014-17617.8/HIGHCISA KEVCWE-787CWE-787

Microsoft Word and Office RTF Memory Corruption Remote Code Execution Vulnerability (CVE-2014-1761) Analysis & Mitigation Guide

⚡ Jump to Patch
Affected Vendors
microsoft
Affected Components
word, office, sharepoint_server, office_web_apps
Published Date
2014-03-25
CVSS v3.1
7.8
HIGH
EPSS (30d)
77.7%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Microsoft Word 2003 to 2013, Office for Mac 2011, SharePoint Server Word Automation Services, and Office Web Apps.

Impact

Remote attackers can execute arbitrary code or cause a denial of service (system crash) by tricking a user into opening a crafted RTF document.

Mitigation

Apply the official MS14-017 security patch immediately, or implement File Block policies to disable RTF parsing in Microsoft Word.

Affected Products & Version Scope

Microsoft Word 2003 SP3, 2007 SP3, 2010 SP1/SP2, 2013, 2013 RT, Word Viewer, Office Compatibility Pack SP3, Office for Mac 2011, SharePoint Server 2010/2013 Word Automation Services, and Office Web Apps 2010/2013.

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

Deploy the official Microsoft security update MS14-017 across all endpoints. In enterprise environments, use WSUS or SCCM to push the updates. For standalone systems, run Windows Update to apply the latest security patches.

2. Temporary Workaround & Hardening Configuration

If patching cannot be immediately performed, use the following PowerShell script to configure the Registry and block Microsoft Word from opening RTF files (File Block policy).

powershell
# Block opening RTF files in Word 2013 via Registry
$registryPath = 'HKCU:\Software\Microsoft\Office\15.0\Word\Security\FileOpenBlock'
if (-not (Test-Path $registryPath)) {
    New-Item -Path $registryPath -Force | Out-Null
}
New-ItemProperty -Path $registryPath -Name 'RtfFiles' -Value 2 -PropertyType DWord -Force
Write-Host 'RTF File Block policy has been successfully applied to Word 2013.'

3. Log Audit & IoC Verification Commands

Verify whether the security patch has been successfully applied by checking the file version of the Word executable (winword.exe).

powershell
# Check the file version of winword.exe to verify MS14-017 patch status
$wordPath = "${env:ProgramFiles}\Microsoft Office\Office15\WINWORD.EXE"
if (Test-Path $wordPath) {
    $fileVersion = (Get-Item $wordPath).VersionInfo.FileVersion
    Write-Host "Current Word Version: $fileVersion"
    # For Word 2013, the secure version after MS14-017 should be 15.0.4611.1001 or higher.
} else {
    Write-Host 'Default Word 2013 path not found. Please verify the installation path manually.'
}
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
As this vulnerability is listed in the CISA KEV catalog, immediately apply the MS14-017 patch or enforce RTF file blocking policies.

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-2014-1761) is an Out-of-bounds Write (CWE-787) memory corruption flaw that exists in Microsoft Word and related Office components when parsing Rich Text Format (RTF) data. The root cause lies in the improper validation of input lengths when processing specific RTF control words or nested structures, allowing an attacker to overwrite memory beyond the allocated buffer boundaries.

2. Exploitation Mechanics & Attack Scenario

An attacker exploits this vulnerability by crafting a malicious RTF document containing specifically structured control words. This document is typically delivered via spear-phishing emails or malicious downloads. If a user previews the email using Microsoft Outlook (which uses Word as the default email viewer) or opens the document in Word, the vulnerability is triggered. This corrupts the heap memory, allowing the attacker to hijack the execution flow and run arbitrary shellcode under the context of the current user. This vulnerability was actively exploited in the wild in March 2014.

3. Infrastructure & Business Impact

Successful exploitation grants the attacker the same privileges as the logged-in user. If the victim is logged in with administrative rights, the attacker can gain full control of the affected system. This includes installing unauthorized programs, viewing, changing, or deleting sensitive data, and establishing a persistent foothold within the corporate network, posing a severe threat to business continuity and data confidentiality.

Official Vendor Advisories & References

NVD Original English Description

Microsoft Word 2003 SP3, 2007 SP3, 2010 SP1 and SP2, 2013, and 2013 RT; Word Viewer; Office Compatibility Pack SP3; Office for Mac 2011; Word Automation Services on SharePoint Server 2010 SP1 and SP2 and 2013; Office Web Apps 2010 SP1 and SP2; and Office Web Apps Server 2013 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted RTF data, as exploited in the wild in March 2014.

Frequently Asked SecOps Questions (CVE-2014-1761)

FAQ

Q1. How critical is CVE-2014-1761 and is it actively exploited in the wild?

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

Q2. Which vendors and products are affected by CVE-2014-1761?

Primary impacted vendors include microsoft across word, office, sharepoint_server, office_web_apps. Scope summary: Microsoft Word 2003 SP3, 2007 SP3, 2010 SP1/SP2, 2013, 2013 RT, Word Viewer, Office Compatibility Pack SP3, Office for Mac 2011, SharePoint Server 2010/2013 Word Automation Services, and Office Web Apps 2010/2013.

Q3. What temporary mitigations or workarounds exist for CVE-2014-1761 before patching?

[Mitigation] Apply the official MS14-017 security patch immediately, or implement File Block policies to disable RTF parsing in Microsoft Word. 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-2014-1761

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-2014-1761 Microsoft Word and Office RTF Memory Corruption Remote Code Execution Vulnerability (CVE-2014-1761) Analysis & Mitigation Guide (CVSS 7.8) - Patch & Workaround | CVE Pulse