# CVE-2006-2492: Microsoft Word Malformed Object Pointer

> User-assisted attackers can execute arbitrary code via a buffer overflow in Microsoft Word triggered by a malformed object pointer.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 8 Jun 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 May 2006
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-pvcc-qqxr-p978

## What is CVE-2006-2492?

CVE-2006-2492 is a high-severity memory corruption vulnerability in Microsoft Office, published on 20 May 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Microsoft Word in Office 2000 SP3, Office XP SP3, Office 2003 Sp1 and SP2, and Microsoft Works Suites through 2006, allows user-assisted attackers to execute arbitrary code via a malformed object pointer, as originally reported by ISC on 20060519 for a zero-day attack.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2006-2492?

It affects 2 products.


Products: Microsoft Office, Microsoft Works Suite.

## How do I fix CVE-2006-2492?

No fix has been published for CVE-2006-2492 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 22 Jun 2022.

## Is CVE-2006-2492 being exploited?

Yes. Attackers have exploited CVE-2006-2492 in the wild since at least 8 Jun 2022.

## 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-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)
- [CVE-2017-8570](https://insights.sbomify.com/CVE-2017-8570/): Microsoft Office Remote Code Execution (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2492 and fix it if it is affected.

What it is: CVE-2006-2492 is a high-severity memory corruption vulnerability in Microsoft Office, published on 20 May 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2006-2492 in the wild since at least 8 Jun 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-2006-2492/ (Markdown: https://insights.sbomify.com/CVE-2006-2492/index.md)
```

## Sources

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

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