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

> Remote attackers can cause denial of service via crafted EMF files exploiting an integer overflow in Windows GDI+.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **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:** 1 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8g6h-gj49-cm84

## What is CVE-2009-1217?

CVE-2009-1217 is a medium-severity vulnerability in n/a, published on 1 Apr 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

Off-by-one error in the GpFont::SetData function in gdiplus.dll in Microsoft GDI+ on Windows XP allows remote attackers to cause a denial of service (stack corruption and application termination) via a crafted EMF file that triggers an integer overflow, as demonstrated by voltage-exploit.emf, aka the "Microsoft GdiPlus EMF GpFont.SetData integer overflow."

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Microsoft Gdi\+.

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

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

## Is CVE-2009-1217 being exploited?

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

Public exploit code:

- Microsoft GdiPlus - EMF GpFont.SetData Integer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1217 is a medium-severity vulnerability in n/a, published on 1 Apr 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-1217 exists.

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

## Sources

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

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