# CVE-2018-1002209: Path traversal in quazip

> Attackers can write to arbitrary files via directory traversal in QuaZIP archives, potentially compromising system integrity.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **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:** 25 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-1002209, GHSA-6f6v-x2xf-m89x, MGASA-2018-0362, UBUNTU-CVE-2018-1002209

## What is CVE-2018-1002209?

CVE-2018-1002209 is a medium-severity path traversal vulnerability in quazip, published on 25 Jul 2018. 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

QuaZIP before 0.7.6 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Quazip Project Quazip.

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

Upgrade to a fixed version.

## Is CVE-2018-1002209 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1002209 is a medium-severity path traversal vulnerability in quazip, published on 25 Jul 2018. 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-2018-1002209 in the wild and no public exploit code.

Affected product: quazip. 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-1002209/ (Markdown: https://insights.sbomify.com/CVE-2018-1002209/index.md)
```

## Sources

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

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