# CVE-2018-1002207: Arbitrary File Write via Archive Extraction in mholt/archiver

> Attackers can write arbitrary files via directory traversal in archive extraction, potentially leading to code execution or data modification.

- **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:** GHSA-5wmg-j84w-4jj4, GO-2022-0799, SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARCHIVER-50071

## What is CVE-2018-1002207?

CVE-2018-1002207 is a medium-severity path traversal vulnerability in golang archiver, 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

mholt/archiver golang package before e4ef56d48eb029648b0e895bb0b6a393ef0829c3 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in an 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-1002207?

3 open source packages ship an affected version, including github.com/mholt/archiver. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mholt/archiver` | Go | All versions | 2.1.0 |
| `github.com/mholt/archiver` | Go | All versions | 2.1.0 |
| `github.com/mholt/archiver` | Go | All versions | 2.1.0+incompatible |

Products: Archiver Project Archiver.

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

Upgrade github.com/mholt/archiver to a fixed version for your release line: 2.1.0 or 2.1.0+incompatible.

## Is CVE-2018-1002207 being exploited?

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

## Other vulnerabilities in golang archiver

- [CVE-2019-10743](https://insights.sbomify.com/CVE-2019-10743/): Path Traversal in MHolt Archiver (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1002207 is a medium-severity path traversal vulnerability in golang archiver, 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-1002207 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mholt/archiver (Go): affected all versions; fixed in 2.1.0
- github.com/mholt/archiver (Go): affected all versions; fixed in 2.1.0
- github.com/mholt/archiver (Go): affected all versions; fixed in 2.1.0+incompatible

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

## Sources

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

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