# CVE-2014-1761: Microsoft Word Memory Corruption

> Remote attackers can execute arbitrary code or cause denial of service via crafted RTF data in Microsoft Word and related Office components.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Feb 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Mar 2014
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-f32r-xw6q-p85m

## What is CVE-2014-1761?

CVE-2014-1761 is a high-severity memory corruption vulnerability in Microsoft Office, published on 24 Mar 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2014-1761?

It affects 7 products.


Products: Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Office Web Apps, Microsoft Office Web Apps Server, Microsoft Sharepoint Server, Microsoft Word, Microsoft Word Viewer.

## How do I fix CVE-2014-1761?

No fix has been published for CVE-2014-1761 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Aug 2022.

## Is CVE-2014-1761 being exploited?

Yes. Attackers have exploited CVE-2014-1761 in the wild since at least 15 Feb 2022.

Public exploit code:

- MS14-017 Microsoft Word RTF Object Confusion (metasploit)
- Microsoft Word - RTF Object Confusion (MS14-017) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1761 and fix it if it is affected.

What it is: CVE-2014-1761 is a high-severity memory corruption vulnerability in Microsoft Office, published on 24 Mar 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2014-1761 in the wild since at least 15 Feb 2022.

Affected product: Microsoft Office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-1761/ (Markdown: https://insights.sbomify.com/CVE-2014-1761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-1761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-1761
- OSV: https://osv.dev/vulnerability/CVE-2014-1761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-1761/
Summaries are generated and may contain mistakes; the official description above is the record.