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

> A buffer overflow in the Tk Toolkit allows attackers to cause a denial of service via a malicious animated GIF file.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5378, DSA-1415-1, DSA-1416-1, GHSA-5mgp-v92x-h349

## What is CVE-2007-5378?

CVE-2007-5378 is a medium-severity memory corruption vulnerability in n/a, published on 12 Oct 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the FileReadGIF function in tkImgGIF.c for Tk Toolkit 8.4.12 and earlier, and 8.3.5 and earlier, allows user-assisted attackers to cause a denial of service (segmentation fault) via an animated GIF in which the first subimage is smaller than a subsequent subimage, which triggers the overflow in the ReadImage function, a different vulnerability than CVE-2007-5137.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Tcl Tk Tk Toolkit.

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

Apply the vendor's patch.

## Is CVE-2007-5378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5378 is a medium-severity memory corruption vulnerability in n/a, published on 12 Oct 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-5378 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-5378/ (Markdown: https://insights.sbomify.com/CVE-2007-5378/index.md)
```

## Sources

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

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