# GHSA-cv3v-7846-6pxm: Unauthorized File Access in node-git-server

> Attackers can access private git repositories via absolute paths in node-git-server, exposing sensitive code without authentication.

- **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:** 3 Sep 2020

## What is GHSA-cv3v-7846-6pxm?

GHSA-cv3v-7846-6pxm is a path traversal vulnerability in node-git-server, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `node-git-server` prior to 0.6.1 are vulnerable to Unauthorized File Access. It is possible to access any git repository by using absolute paths, which may allow attackers to access private repositories.

## Recommendation

Upgrade to version 0.6.1 or later.

## Which versions are affected by GHSA-cv3v-7846-6pxm?

2 open source packages ship an affected version, including node-git-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-git-server` | npm | From 0.2.0 | 0.6.1 |
| `node-git-server` | npm | From 0.2.0 | 0.6.1 |

## How do I fix GHSA-cv3v-7846-6pxm?

Upgrade node-git-server to 0.6.1 or later.

## Is GHSA-cv3v-7846-6pxm being exploited?

There is no known exploitation of GHSA-cv3v-7846-6pxm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cv3v-7846-6pxm and fix it if it is affected.

What it is: GHSA-cv3v-7846-6pxm is a path traversal vulnerability in node-git-server, published on 3 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-cv3v-7846-6pxm in the wild and no public exploit code.

Affected packages and fixed versions:
- node-git-server (npm): affected from 0.2.0; fixed in 0.6.1
- node-git-server (npm): affected from 0.2.0; fixed in 0.6.1

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-cv3v-7846-6pxm/ (Markdown: https://insights.sbomify.com/GHSA-cv3v-7846-6pxm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cv3v-7846-6pxm

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