# GHSA-vc6r-4x6g-mmqc: Path Traversal in m-server

> A remote attacker can exploit a path traversal vulnerability in m-server to read arbitrary files from the server.

- **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:** 11 Jun 2019

## What is GHSA-vc6r-4x6g-mmqc?

GHSA-vc6r-4x6g-mmqc is a path traversal vulnerability in m-server, published on 11 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `m-server` before 1.4.2 are vulnerable to path traversal allowing a remote attacker to display content of arbitrary files from the server.

## Recommendation

Update to version 1.4.2 or later.

## Which versions are affected by GHSA-vc6r-4x6g-mmqc?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `m-server` | npm | All versions | 1.4.2 |
| `m-server` | npm | All versions | 1.4.2 |

## How do I fix GHSA-vc6r-4x6g-mmqc?

Upgrade m-server to 1.4.2 or later.

## Is GHSA-vc6r-4x6g-mmqc being exploited?

There is no known exploitation of GHSA-vc6r-4x6g-mmqc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vc6r-4x6g-mmqc and fix it if it is affected.

What it is: GHSA-vc6r-4x6g-mmqc is a path traversal vulnerability in m-server, published on 11 Jun 2019. 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-vc6r-4x6g-mmqc in the wild and no public exploit code.

Affected packages and fixed versions:
- m-server (npm): affected all versions; fixed in 1.4.2
- m-server (npm): affected all versions; fixed in 1.4.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-vc6r-4x6g-mmqc/ (Markdown: https://insights.sbomify.com/GHSA-vc6r-4x6g-mmqc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vc6r-4x6g-mmqc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-vc6r-4x6g-mmqc/
Summaries are generated and may contain mistakes; the official description above is the record.