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

> An integer overflow in the exiftags library causes illegal memory access, potentially leading to crashes or undefined behavior when processing malformed EXIF data.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6355, GHSA-pg5q-fr6h-gjf4

## What is CVE-2007-6355?

CVE-2007-6355 is a critical vulnerability in n/a, published on 18 Dec 2007. 

### Official description

Integer overflow in exiftags before 1.01 has unknown impact and attack vectors, resulting from a "field offset overflow" that triggers an "illegal memory access," a different vulnerability than CVE-2007-6354.

Weakness: CWE-189

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

It affects 1 product.


Products: Aertherwide Exiftags.

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

Upgrade to a fixed version.

## Is CVE-2007-6355 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6354](https://insights.sbomify.com/CVE-2007-6354/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-42851](https://insights.sbomify.com/CVE-2024-42851/): Memory corruption in n/a (high 8.4)
- [CVE-2023-50671](https://insights.sbomify.com/CVE-2023-50671/): Memory corruption in n/a (high 7.8)
- [CVE-2007-6356](https://insights.sbomify.com/CVE-2007-6356/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6355 is a critical vulnerability in n/a, published on 18 Dec 2007. 
Exploitation: There is no known exploitation of CVE-2007-6355 in the wild and no public exploit code.

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-6355/ (Markdown: https://insights.sbomify.com/CVE-2007-6355/index.md)
```

## Sources

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

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