CVE-2001-0450
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 Transsoft FTP Broker before 5.5 allows attackers to (1) delete arbitrary files via DELETE, or (2) list arbitrary directories via LIST, via a .. (dot dot) in the file name.
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 confidenceDirectory traversal vulnerability in Transsoft FTP Broker before version 5.5 allows attackers to manipulate file paths using '..' (dot dot) sequences. Specifically, the DELETE command can be used to delete arbitrary files outside the intended directory, and the LIST command can be used to enumerate contents of arbitrary directories on the filesystem.
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<= 5.5CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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 Transsoft FTP Broker installationSearch for Transsoft FTP Broker process running on the system, or look for installation directories named 'Transsoft' or 'FTP Broker' in Program Files or system directories. Also check Windows Services for a service named 'Transsoft FTP Broker' or similar.Affected if Transsoft FTP Broker is found running or installed on the system
-
Determine installed versionCheck the version of the Transsoft FTP Broker executable (typically named ftpbroker.exe or similar) by right-clicking the file and selecting Properties, or running 'ftpbroker.exe -v' from the command line if supported.Affected if The version cannot be determined or is 5.5 or lower
-
Compare version to affected rangeReview the version number against the affected range: versions before 5.5 are vulnerable. Version 5.5 and later are patched.Affected if Installed version is 5.5 or lower (any version before 5.5)
-
Verify FTP service is accessibleConfirm the FTP service is running and accepting connections by attempting to connect to the FTP port (default port 21) on the server where Transsoft is installed.Affected if FTP service is active and the installed version is 5.5 or lower, exposing the vulnerability
The environment is affected if Transsoft FTP Broker is installed with version 5.5 or lower, and the FTP service is accessible.
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 to Transsoft FTP Broker version 5.5 or later, which contains the patch for this vulnerability. If the product is no longer supported, migrate to a maintained FTP server solution with current security updates.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0450 — 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-2001-0450 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