# CVE-2009-0562: Memory corruption in n/a

> Remote attackers can execute arbitrary code via memory corruption in Office Web Components ActiveX controls, requiring user interaction to trigger.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wvqf-rrqc-53gr

## What is CVE-2009-0562?

CVE-2009-0562 is a critical memory corruption vulnerability in Microsoft Office, published on 12 Aug 2009. 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

The Office Web Components ActiveX Control in Microsoft Office XP SP3, Office 2003 SP3, Office XP Web Components SP3, Office 2003 Web Components SP3, Office 2003 Web Components SP1 for the 2007 Microsoft Office System, Internet Security and Acceleration (ISA) Server 2004 SP3 and 2006 SP1, and Office Small Business Accounting 2006 does not properly allocate memory, which allows remote attackers to execute arbitrary code via unspecified vectors that trigger "system state" corruption, aka "Office Web Components Memory Allocation Vulnerability."

Weakness: CWE-399

## Which versions are affected by CVE-2009-0562?

It affects 3 products.


Products: Microsoft Isa Server, Microsoft Office, Microsoft Office Web Components.

## How do I fix CVE-2009-0562?

No fix has been published for CVE-2009-0562 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-0562 being exploited?

There is no known exploitation of CVE-2009-0562 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Office

- [CVE-2006-7027](https://insights.sbomify.com/CVE-2006-7027/): Microsoft Internet Security and Acceleration (ISA) Server 2004 logs unusual ASCII characters in the Host header, including the tab, which al (critical 10.0)
- [CVE-2009-1534](https://insights.sbomify.com/CVE-2009-1534/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-1136](https://insights.sbomify.com/CVE-2009-1136/): Code injection in n/a (critical 9.3)
- [CVE-2009-1135](https://insights.sbomify.com/CVE-2009-1135/): Auth bypass in n/a (critical 9.0)
- [CVE-2006-3652](https://insights.sbomify.com/CVE-2006-3652/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0562 and fix it if it is affected.

What it is: CVE-2009-0562 is a critical memory corruption vulnerability in Microsoft Office, published on 12 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-0562 in the wild and no public exploit code.

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-2009-0562/ (Markdown: https://insights.sbomify.com/CVE-2009-0562/index.md)
```

## Sources

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

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