dbcve.org
FerryApplication · Ferry Project

CVE-2022-3939

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A path traversal vulnerability exists in the Ferry file management system's public API (apis/public/file.go). The 'file' argument in an unknown function is not properly validated, allowing attackers to manipulate file paths using sequences like '../' to access files outside the intended directory. This can be exploited remotely with critical impact due to the ability to read sensitive system files.

MitigationImplement strict input validation and path canonicalization: validate that the resolved canonical path stays within the intended directory, reject any path containing traversal sequences, and use secure file serving methods that prevent directory escape.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FerryApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ferry installation
    Check if the Ferry file management system is installed in your environment by searching for Ferry binaries, containers, or services (e.g., search for 'ferry' in running processes, installed packages, or container images).
    Affected if Ferry is present in your environment.
  2. Identify Ferry version
    Run 'ferry --version' or check the installed package version through your package manager (e.g., docker images, npm list, pip show). If the binary is available, use any available version flag.
    Affected if Any version of Ferry is installed (all versions are affected per the CVE).
  3. Verify vulnerable API file exists
    Locate the source or binary containing apis/public/file.go in your Ferry installation. Check if this file is present in the codebase or compiled into the running binary.
    Affected if The file apis/public/file.go exists in your Ferry installation.
  4. Check public API accessibility
    Determine if the public API endpoint (apis/public/) is exposed and accessible from your network. Check your web server configuration, firewall rules, or API gateway settings for routes under /public/.
    Affected if The public API is accessible over the network (this enables remote exploitation).
  5. Verify file serving is enabled
    Check Ferry configuration files or runtime settings to determine if the file serving functionality that uses the vulnerable 'file' parameter is enabled or in use.
    Affected if File serving through the public API is enabled or operational.

If Ferry is installed and its public API with file serving is accessible, your environment is vulnerable to path traversal attacks and should be investigated.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and path canonicalization: validate that the resolved canonical path stays within the intended directory, reject any path containing traversal sequences, and use secure file serving methods that prevent directory escape.

Fix this in Ferry Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3939 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data