# GHSA-6jrj-vc65-c983: unzip-stream allows Arbitrary File Write via artifact extraction

> Attackers can write arbitrary files via malicious zip archives, potentially leading to code execution or data modification.

- **Severity:** Not scored
- **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:** 26 Aug 2024

## What is GHSA-6jrj-vc65-c983?

GHSA-6jrj-vc65-c983 is a path traversal vulnerability in unzip-stream, published on 26 Aug 2024. 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

### Impact

When using the `Extract()` method of unzip-stream, malicious zip files were able to write to paths they shouldn't be allowed to.

### Patches

Fixed in 0.3.2

### References

- https://snyk.io/research/zip-slip-vulnerability
- https://github.com/mhr3/unzip-stream/compare/v0.3.1...v0.3.2

### Credits

Justin Taft from Google

## Which versions are affected by GHSA-6jrj-vc65-c983?

2 open source packages ship an affected version, including unzip-stream.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `unzip-stream` | npm | All versions | 0.3.2 |
| `unzip-stream` | npm | All versions | 0.3.2 |

## How do I fix GHSA-6jrj-vc65-c983?

Upgrade unzip-stream to 0.3.2 or later.

## Is GHSA-6jrj-vc65-c983 being exploited?

There is no known exploitation of GHSA-6jrj-vc65-c983 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6jrj-vc65-c983 and fix it if it is affected.

What it is: GHSA-6jrj-vc65-c983 is a path traversal vulnerability in unzip-stream, published on 26 Aug 2024. 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 GHSA-6jrj-vc65-c983 in the wild and no public exploit code.

Affected packages and fixed versions:
- unzip-stream (npm): affected all versions; fixed in 0.3.2
- unzip-stream (npm): affected all versions; fixed in 0.3.2

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/GHSA-6jrj-vc65-c983/ (Markdown: https://insights.sbomify.com/GHSA-6jrj-vc65-c983/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6jrj-vc65-c983

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6jrj-vc65-c983/
Summaries are generated and may contain mistakes; the official description above is the record.