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

> Remote attackers can execute arbitrary code by tricking users into opening a crafted Visio file, requiring user interaction.

- **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:** 10 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3jqr-q83p-f9r3

## What is CVE-2009-0097?

CVE-2009-0097 is a critical memory corruption vulnerability in Microsoft Visio, published on 10 Feb 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

Microsoft Office Visio 2002 SP2 and 2003 SP3 does not properly validate memory allocation for Visio files, which allows remote attackers to execute arbitrary code via a crafted file, aka "Memory Corruption Vulnerability."

Weakness: CWE-399

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

It affects 1 product.


Products: Microsoft Visio.

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

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

## Is CVE-2009-0097 being exploited?

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

## Other vulnerabilities in Microsoft Visio

- [CVE-2016-3235](https://insights.sbomify.com/CVE-2016-3235/): Microsoft Office OLE DLL Side Loading (high 7.8, exploited in the wild)
- [CVE-2015-2557](https://insights.sbomify.com/CVE-2015-2557/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-1888](https://insights.sbomify.com/CVE-2012-1888/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-1972](https://insights.sbomify.com/CVE-2011-1972/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-1979](https://insights.sbomify.com/CVE-2011-1979/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0097 is a critical memory corruption vulnerability in Microsoft Visio, published on 10 Feb 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-0097 in the wild and no public exploit code.

Affected product: Microsoft Visio. 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-0097/ (Markdown: https://insights.sbomify.com/CVE-2009-0097/index.md)
```

## Sources

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

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