# CVE-2009-2518: Integer overflow in n/a

> Remote attackers can execute arbitrary code via a malicious Office document containing a crafted BMP image due to an integer overflow in GDI+.

- **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:** 14 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j2jw-vxpm-g78j

## What is CVE-2009-2518?

CVE-2009-2518 is a critical vulnerability in Microsoft Office, published on 14 Oct 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

Integer overflow in GDI+ in Microsoft Office XP SP3 allows remote attackers to execute arbitrary code via an Office document with a bitmap (aka BMP) image that triggers memory corruption, aka "Office BMP Integer Overflow Vulnerability."

Weakness: CWE-189

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

It affects 1 product.


Products: Microsoft Office.

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

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

## Is CVE-2009-2518 being exploited?

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

## 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-2009-2518 and fix it if it is affected.

What it is: CVE-2009-2518 is a critical vulnerability in Microsoft Office, published on 14 Oct 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-2518 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-2518/ (Markdown: https://insights.sbomify.com/CVE-2009-2518/index.md)
```

## Sources

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

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