# CVE-2022-3939: lanyulei ferry API file.go path traversal

> Remote attackers can exploit a path traversal vulnerability in the ferry API to read arbitrary files from the server.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-q939-gqg6-jqvf

## What is CVE-2022-3939?

CVE-2022-3939 is a medium-severity path traversal vulnerability in lanyulei ferry, published on 11 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in lanyulei ferry. Affected by this issue is some unknown functionality of the file apis/public/file.go of the component API. The manipulation of the argument file leads to path traversal. The attack may be launched remotely. VDB-213446 is the identifier assigned to this vulnerability.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-3939?

It affects 1 product.


Products: Ferry Project Ferry.

## How do I fix CVE-2022-3939?

No fix has been published for CVE-2022-3939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3939 being exploited?

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

## Other vulnerabilities in lanyulei ferry

- [CVE-2022-3940](https://insights.sbomify.com/CVE-2022-3940/): lanyulei ferry task.go path traversal (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3939 and fix it if it is affected.

What it is: CVE-2022-3939 is a medium-severity path traversal vulnerability in lanyulei ferry, published on 11 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3939 in the wild and no public exploit code.

Affected product: lanyulei ferry. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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