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

> A stack-based buffer overflow in ZZIPlib allows remote attackers to execute arbitrary code or crash applications via a long filename, requiring user interaction.

- **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:** 23 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1614, DTSA-56-1, GHSA-w963-353v-jm7m

## What is CVE-2007-1614?

CVE-2007-1614 is a critical memory corruption vulnerability in n/a, published on 23 Mar 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

Stack-based buffer overflow in the zzip_open_shared_io function in zzip/file.c in ZZIPlib Library before 0.13.49 allows user-assisted remote attackers to cause a denial of service (application crash) or execute arbitrary code via a long filename.

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

It affects 1 product.


Products: Zziplib Zziplib.

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

Upgrade to a fixed version.

## Is CVE-2007-1614 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1614 is a critical memory corruption vulnerability in n/a, published on 23 Mar 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: There is no known exploitation of CVE-2007-1614 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-1614/ (Markdown: https://insights.sbomify.com/CVE-2007-1614/index.md)
```

## Sources

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

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