CVE-2020-14057
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 · uneditedMonsta FTP 2.10.1 or below allows external control of paths used in filesystem operations. This allows attackers to read and write arbitrary local files, allowing an attacker to gain remote code execution in common deployments.
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 · high confidenceMonsta FTP 2.10.1 and below contains a path traversal vulnerability that allows external control of paths in filesystem operations. Attackers can manipulate file paths to read or write arbitrary local files on the server, leading to remote code execution in typical deployments.
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<= 2.10.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Monsta FTP installationLocate the Monsta FTP application on the system. Check for its web files (typically in a web server document root) or look for the Monsta FTP service process.Affected if Monsta FTP software is present on the system
-
Identify installed versionCheck the version information for Monsta FTP. This is usually displayed in the web interface footer, or can be found in version files within the installation directory.Affected if The installed version is 2.10.1 or lower
-
Verify web interface accessibilityDetermine if the Monsta FTP web interface is accessible over the network. Check network bindings and firewall rules to see if the interface is exposed to untrusted networks.Affected if The web interface is reachable from network locations beyond the trusted internal network
-
Check authentication configurationReview the authentication settings for Monsta FTP to determine if anonymous or default credentials are enabled, which would allow unauthenticated access to file operations.Affected if Anonymous access is enabled or weak authentication is configured
-
Assess input validation controlsInspect whether custom input validation or web application firewall rules are in place to filter directory traversal patterns (such as ../ sequences) from file path parameters.Affected if No input validation or filtering mechanisms are implemented to block path traversal attempts
You are affected if Monsta FTP version 2.10.1 or below is installed and its web interface is accessible, particularly without proper input validation on file path parameters.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Monsta FTP to a version above 2.10.1. If immediate patching is not possible, restrict network access to the FTP interface and implement strict input validation on all file path parameters to prevent directory traversal.
Latest stable release above 2.10.1 (check official Monsta FTP channels for exact current version)
- 1. Backup your current Monsta FTP installation and configuration
- 2. Download the latest version of Monsta FTP from the official source at www.monstaftp.com or the official GitHub repository
- 3. Replace the existing Monsta FTP files with the new version, preserving your configuration
- 4. Verify the upgrade was successful by logging into the FTP application
- 5. Test that file operations work correctly and the vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14057 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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