# CVE-2010-3333: Microsoft Office Stack-based Buffer Overflow

> Remote attackers can execute arbitrary code via crafted RTF data due to a stack-based buffer overflow in Microsoft Office.

- **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 3 Mar 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:** 10 Nov 2010
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-r838-75c6-gjj4

## What is CVE-2010-3333?

CVE-2010-3333 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Nov 2010. 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

Stack-based buffer overflow in Microsoft Office XP SP3, Office 2003 SP3, Office 2007 SP2, Office 2010, Office 2004 and 2008 for Mac, Office for Mac 2011, and Open XML File Format Converter for Mac allows remote attackers to execute arbitrary code via crafted RTF data, aka "RTF Stack Buffer Overflow Vulnerability."

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

## Which versions are affected by CVE-2010-3333?

It affects 2 products.


Products: Microsoft Office, Microsoft Open Xml File Format Converter.

## How do I fix CVE-2010-3333?

No fix has been published for CVE-2010-3333 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2010-3333 being exploited?

Yes. Attackers have exploited CVE-2010-3333 in the wild since at least 3 Mar 2022.

Public exploit code:

- CVE-2010-3333复现 (github_poc): https://github.com/Sunqiz/CVE-2010-3333-reproduction
- MS10-087 Microsoft Word RTF pFragments Stack Buffer Overflow (File Format) (metasploit)
- Microsoft Word - '.RTF' pFragments Stack Buffer Overflow (File Format) (MS10-087) (Metasploit) (exploitdb)
- Microsoft Office 2010 - '.RTF' Header Stack Overflow (exploitdb)
- Microsoft Office 2003 Home/Pro - Code Execution (MS10-087) (exploitdb)
- Microsoft Office 2010 - Download Execute (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-2010-3333 and fix it if it is affected.

What it is: CVE-2010-3333 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Nov 2010. 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-2010-3333 in the wild since at least 3 Mar 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-2010-3333/ (Markdown: https://insights.sbomify.com/CVE-2010-3333/index.md)
```

## Sources

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

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