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

> Remote attackers can execute arbitrary code via crafted TIFF images due to improper buffer allocation in GDI+, affecting Windows and Office applications.

- **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-cfgp-6px9-h8qc

## What is CVE-2009-2503?

CVE-2009-2503 is a critical memory corruption vulnerability in Microsoft .Net Framework, 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

GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Windows Server 2003 SP2, Office XP SP3, Office 2003 SP3, 2007 Microsoft Office System SP1 and SP2, Office Project 2002 SP1, Visio 2002 SP2, Office Word Viewer, Word Viewer 2003 Gold and SP3, Office Excel Viewer 2003 Gold and SP3, Office Excel Viewer, Office PowerPoint Viewer 2007 Gold, SP1, and SP2, Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP1 and SP2, Expression Web, Expression Web 2, Groove 2007 Gold and SP1, Works 8.5, SQL Server 2000 Reporting Services SP2, SQL Server 2005 SP2 and SP3, Report Viewer 2005 SP1, Report Viewer 2008 Gold and SP1, and Forefront Client Security 1.0 does not properly allocate an unspecified buffer, which allows remote attackers to execute arbitrary code via a crafted TIFF image file that triggers memory corruption, aka "GDI+ TIFF Memory Corruption Vulnerability."

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

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

It affects 26 products.


Products: Microsoft .Net Framework, Microsoft Excel Viewer, Microsoft Expression Web, Microsoft Forefront Client Security, Microsoft Internet Explorer, Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Office Excel Viewer, Microsoft Office Groove, Microsoft Office Powerpoint Viewer, Microsoft Office Word Viewer, Microsoft Platform Sdk, Microsoft Project, Microsoft Report Viewer, Microsoft Sql Server, Microsoft Sql Server Reporting Services, Microsoft Visio, Microsoft Visual Foxpro, Microsoft Visual Studio, Microsoft Visual Studio .Net and 6 more.

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

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

## Is CVE-2009-2503 being exploited?

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

## Other vulnerabilities in Microsoft .Net Framework

- [CVE-2020-0646](https://insights.sbomify.com/CVE-2020-0646/): Microsoft .NET Framework Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-8759](https://insights.sbomify.com/CVE-2017-8759/): Microsoft .NET Framework Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2015-1671](https://insights.sbomify.com/CVE-2015-1671/): Microsoft Windows Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2024-29059](https://insights.sbomify.com/CVE-2024-29059/): Microsoft .NET Framework Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2014-4073](https://insights.sbomify.com/CVE-2014-4073/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2503 is a critical memory corruption vulnerability in Microsoft .Net Framework, 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-2503 in the wild and no public exploit code.

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

## Sources

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

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