# GHSA-2mj8-pj3j-h362: Symlink reference outside of node_modules in bin-links

> Attackers can create symlinks to files outside node_modules via the bin field, allowing unauthorized file access.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2020

## What is GHSA-2mj8-pj3j-h362?

GHSA-2mj8-pj3j-h362 is a path traversal vulnerability in bin-links, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `bin-links` prior to 1.1.5 are vulnerable to a Symlink reference outside of node_modules. It is possible to create symlinks to files outside of the`node_modules` folder through the `bin` field. This may allow attackers to access unauthorized files.

## Recommendation

Upgrade to version 1.1.5 or later.

## Which versions are affected by GHSA-2mj8-pj3j-h362?

2 open source packages ship an affected version, including bin-links.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bin-links` | npm | All versions | 1.1.5 |
| `bin-links` | npm | All versions | 1.1.5 |

## How do I fix GHSA-2mj8-pj3j-h362?

Upgrade bin-links to 1.1.5 or later.

## Is GHSA-2mj8-pj3j-h362 being exploited?

There is no known exploitation of GHSA-2mj8-pj3j-h362 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2mj8-pj3j-h362 and fix it if it is affected.

What it is: GHSA-2mj8-pj3j-h362 is a path traversal vulnerability in bin-links, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2mj8-pj3j-h362 in the wild and no public exploit code.

Affected packages and fixed versions:
- bin-links (npm): affected all versions; fixed in 1.1.5
- bin-links (npm): affected all versions; fixed in 1.1.5

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-2mj8-pj3j-h362/ (Markdown: https://insights.sbomify.com/GHSA-2mj8-pj3j-h362/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2mj8-pj3j-h362

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2mj8-pj3j-h362/
Summaries are generated and may contain mistakes; the official description above is the record.