# CVE-2009-1136: Code injection in n/a

> Remote attackers can execute arbitrary code via a crafted call in the Office Web Components Spreadsheet ActiveX control when used in Internet Explorer.

- **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:** 15 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3vw3-8gqg-phx5

## What is CVE-2009-1136?

CVE-2009-1136 is a critical code injection vulnerability in Microsoft Office, published on 15 Jul 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 Microsoft Office Web Components Spreadsheet ActiveX control (aka OWC10 or OWC11), as distributed in Office XP SP3 and 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 Gold and SP1, and Office Small Business Accounting 2006, when used in Internet Explorer, allows remote attackers to execute arbitrary code via a crafted call to the msDataSourceObject method, as exploited in the wild in July and August 2009, aka "Office Web Components HTML Script Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 4 products.


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

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

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

## Is CVE-2009-1136 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1136 exists.

Public exploit code:

- Microsoft OWC Spreadsheet msDataSourceObject Memory Corruption (metasploit)
- Microsoft Office Web Components (OWC) Spreadsheet - ActiveX Buffer Overflow (PoC) (exploitdb)
- Microsoft Office Web Components (OWC) Spreadsheet - msDataSourceObject Memory Corruption (MS09-043) (Metasploit) (exploitdb)

## 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-0562](https://insights.sbomify.com/CVE-2009-0562/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-1534](https://insights.sbomify.com/CVE-2009-1534/): Memory corruption 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-1136 and fix it if it is affected.

What it is: CVE-2009-1136 is a critical code injection vulnerability in Microsoft Office, published on 15 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1136 exists.

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

## Sources

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

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