CVE-2010-4154
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 · uneditedDirectory traversal vulnerability in Rhino Software, Inc. FTP Voyager 15.2.0.11, and possibly earlier, allows remote FTP servers to write arbitrary files via a "..\" (dot dot backslash) in a filename.
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 confidenceFTP Voyager client contains a directory traversal vulnerability allowing malicious FTP servers to write arbitrary files to the client filesystem by using '..\' sequences in filenames during file transfers. This client-side vulnerability enables remote code execution by writing malicious files to startup locations or system directories.
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<= 15.2.0.11= 15.0.0.0= 15.0.0.1= 15.0.0.2= 15.0.0.3= 15.1.0.0= 15.1.0.1= 15.1.0.2= 15.1.0.3= 15.1.0.4= 15.2.0.0= 15.2.0.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Locate FTP Voyager installationSearch for 'FTP Voyager' or 'FtpVoyager' in the program files directory (typically C:\Program Files\Rhinosoft or C:\Program Files\FTP Voyager) and check for the executable fileAffected if FTP Voyager executable is found on the system
-
Determine installed versionRight-click the FTP Voyager executable, select Properties, and view the Details tab for version information. Alternatively, launch the application and check Help > About for the exact version numberAffected if Version matches any of these: 15.0.0.0, 15.0.0.1, 15.0.0.2, 15.0.0.3, 15.1.0.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.2.0.0, 15.2.0.2, or any version <= 15.2.0.11
-
Verify FTP client is configured for server connectionsCheck if FTP Voyager profiles or scheduled tasks exist that connect to remote FTP servers. Open the application and review the site profile list or connection profilesAffected if Any FTP server profiles are configured and active
-
Confirm transfer behavior settingsReview FTP Voyager connection settings or site profiles for any options that control file write operations during downloadsAffected if Download or file transfer functionality is enabled for remote FTP servers
The system is affected if FTP Voyager version 15.0.0.0 through 15.2.0.11 (including the specific listed versions) is installed and configured to connect to FTP servers, allowing malicious servers to write files outside the intended download directory via directory traversal sequences.
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.
From vendor dataUpgrade FTP Voyager to the latest version if available, or migrate to a secure alternative FTP client. Consider replacing FTP with SFTP/SCP protocols for secure file transfers.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4154 — 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-2010-4154 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