# CVE-2007-2217: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted TIFF files exploiting memory corruption in Kodak Image Viewer on Windows.

- **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:** 9 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rp3r-mxcw-m2v4

## What is CVE-2007-2217?

CVE-2007-2217 is a critical memory corruption vulnerability in n/a, published on 9 Oct 2007. 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

Kodak Image Viewer in Microsoft Windows 2000 SP4, and in some cases XP SP2 and Server 2003 SP1 and SP2, allows remote attackers to execute arbitrary code via crafted image files that trigger memory corruption, as demonstrated by a certain .tif (TIFF) file.

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

## Which versions are affected by CVE-2007-2217?

It affects 1 product.


Products: Kodak Image Viewer.

## How do I fix CVE-2007-2217?

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

## Is CVE-2007-2217 being exploited?

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

Public exploit code:

- Kodak Image Viewer - TIF/TIFF Code Execution (MS07-055) (exploitdb)
- Microsoft Internet Explorer - TIF/TIFF Code Execution (MS07-055) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2217 and fix it if it is affected.

What it is: CVE-2007-2217 is a critical memory corruption vulnerability in n/a, published on 9 Oct 2007. 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-2007-2217 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-2007-2217/ (Markdown: https://insights.sbomify.com/CVE-2007-2217/index.md)
```

## Sources

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

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