Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Remote Code Execution in Microsoft Word via Crafted RTF Data

IdentifiersCVE-2014-1761CWE-119

CVE-2014-1761 is a memory-corruption vulnerability in Microsoft Word and related Office components triggered by opening or processing specially crafted Rich Text Format (RTF) content. Affected products include Microsoft Word 2003 SP3, 2007 SP3, 2010 SP1/SP2, 2013, and 2013 RT; Word Viewer; Office Compatibility Pack SP3; Office for Mac 2011; Word Automation Services on SharePoint Server 2010 SP1/SP2 and 2013; Office Web Apps 2010 SP1/SP2; and Office Web Apps Server 2013. The flaw allows a remote attacker to supply malicious RTF data that causes memory corruption during document parsing, which can result in arbitrary code execution or denial of service. The vulnerability was exploited in the wild as a zero-day in March 2014 and was widely used in spearphishing campaigns by multiple threat actors.

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 can allow arbitrary code execution in the context of the user opening the malicious document or the service account processing the document in server-side Office components. In practical attack chains, this enables initial compromise through phishing attachments, malware installation, persistence staging, credential theft, espionage tooling deployment, or broader follow-on intrusion activity. Where code execution is not achieved reliably, the vulnerability can also cause application instability or denial of service due to memory corruption.

Mitigation

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

Until patching is complete, reduce exposure by blocking or quarantining RTF attachments at email gateways, disabling or restricting opening of RTF documents from untrusted sources, and using Protected View or equivalent document isolation controls where available. Limit use of Word Viewer and legacy Office components, and restrict server-side processing of untrusted Office documents in SharePoint or Office Web Apps environments. User awareness against spearphishing attachments can reduce exploitation opportunities, but should not be relied on as a primary control.

Remediation

Patch, then assume compromise.

Apply Microsoft's security update for CVE-2014-1761 across all affected Office products and related components, including desktop Word installations, Word Viewer, Office Compatibility Pack, Office for Mac 2011, SharePoint Word Automation Services, and Office Web Apps / Office Web Apps Server deployments. Ensure unsupported Office versions are retired or isolated. Verify that all document-processing servers handling RTF content are patched, not only user workstations.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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 CorporationOffice Web Appsapplication
Microsoft CorporationOffice Web Apps Serverapplication
Microsoft CorporationSharepoint Serverapplication
Microsoft CorporationWordapplication
Microsoft CorporationWord Viewerapplication

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 evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware5

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

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 activity

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