# CVE-2014-9913: Memory corruption in n/a

> Remote attackers can cause a denial of service via a buffer overflow in the list_files function of Info-Zip UnZip.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2014-9913, AZL-35335, AZL-6937, DEBIAN-CVE-2014-9913, GHSA-7vv9-r95r-f25f, UBUNTU-CVE-2014-9913

## What is CVE-2014-9913?

CVE-2014-9913 is a medium-severity memory corruption vulnerability in n/a, published on 18 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in the list_files function in list.c in Info-Zip UnZip 6.0 allows remote attackers to cause a denial of service (crash) via vectors related to the compression method.

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

## Which versions are affected by CVE-2014-9913?

It affects 1 product.


Products: Unzip Project Unzip.

## How do I fix CVE-2014-9913?

Apply the vendor's patch.

## Is CVE-2014-9913 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36561](https://insights.sbomify.com/CVE-2020-36561/): Path traversal in github.com/yi-ge/unzip (critical 9.1)
- [CVE-2018-1000035](https://insights.sbomify.com/CVE-2018-1000035/): Memory corruption in n/a (high 7.8)
- [CVE-2018-18384](https://insights.sbomify.com/CVE-2018-18384/): Memory corruption in n/a (medium 5.5)
- [CVE-2016-9844](https://insights.sbomify.com/CVE-2016-9844/): Memory corruption in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9913 and fix it if it is affected.

What it is: CVE-2014-9913 is a medium-severity memory corruption vulnerability in n/a, published on 18 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9913 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-2014-9913/ (Markdown: https://insights.sbomify.com/CVE-2014-9913/index.md)
```

## Sources

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

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