# CVE-2007-2645: Integer overflow in n/a

> Integer overflow in libexif allows remote attackers to execute arbitrary code or cause denial of service via crafted EXIF data.

- **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:** Yes
- **Published:** 14 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2645, GHSA-5x4g-m68v-9h8f

## What is CVE-2007-2645?

CVE-2007-2645 is a critical vulnerability in n/a, published on 14 May 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

Integer overflow in the exif_data_load_data_entry function in exif-data.c in libexif before 0.6.14 allows user-assisted remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via crafted EXIF data, involving the (1) doff or (2) s variable.

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

It affects 1 product.


Products: Libexif Libexif.

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

Upgrade to a fixed version.

## Is CVE-2007-2645 being exploited?

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

Public exploit code:

- LibEXIF 0.6.x - Exif_Data_Load_Data_Entry Remote Integer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6352](https://insights.sbomify.com/CVE-2007-6352/): Integer overflow in n/a (medium 6.8)
- [CVE-2006-4168](https://insights.sbomify.com/CVE-2006-4168/): Integer overflow in n/a (medium 6.8)
- [CVE-2005-0664](https://insights.sbomify.com/CVE-2005-0664/): Memory corruption in n/a (low 2.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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