# CVE-2018-13410: Use after free in n/a

> Attackers can cause a denial of service via invalid free in Info-ZIP Zip when using specific command-line options, requiring user interaction with untrusted inputs.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jul 2018
- **Updated:** 18 Sep 2026
- **Also known as:** AZL-35398, AZL-7012, DEBIAN-CVE-2018-13410, ECHO-87cd-2f0b-7f87, GHSA-q826-v3v4-6jvj, MGASA-2026-0406, UBUNTU-CVE-2018-13410

## What is CVE-2018-13410?

CVE-2018-13410 is a critical use after free vulnerability in n/a, published on 6 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Info-ZIP Zip 3.0, when the -T and -TT command-line options are used, allows attackers to cause a denial of service (invalid free and application crash) or possibly have unspecified other impact because of an off-by-one error. NOTE: it is unclear whether there are realistic scenarios in which an untrusted party controls the -TT value, given that the entire purpose of -TT is execution of arbitrary commands

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2018-13410?

It affects 1 product.


Products: Info-Zip Project Zip.

## How do I fix CVE-2018-13410?

Apply the vendor's patch.

## Is CVE-2018-13410 being exploited?

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

Public exploit code:

- patch to fix CVE-2018-13410 of zip-30 (github_poc): https://github.com/shinecome/zip

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13410 and fix it if it is affected.

What it is: CVE-2018-13410 is a critical use after free vulnerability in n/a, published on 6 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-13410 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-2018-13410/ (Markdown: https://insights.sbomify.com/CVE-2018-13410/index.md)
```

## Sources

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

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