CVE-2000-0084
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 · uneditedCuteFTP uses weak encryption to store password information in its tree.dat file.
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 confidenceCuteFTP, an FTP client application, stored user passwords in a file named tree.dat using weak encryption that could be easily reverse-engineered or cracked, allowing local attackers to recover stored FTP credentials.
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.xCVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 CuteFTP installation directorySearch the system for CuteFTP installation folders, typically under Program Files on Windows systems. Check common paths like C:\Program Files\GlobalSCAPE\ or C:\Program Files\CuteFTP\Affected if CuteFTP version 2.x or earlier is installed on the system
-
Find tree.dat fileSearch for a file named tree.dat within the CuteFTP installation directory or user data folders. This file is typically located in the application directory or user profile folders where CuteFTP stores configuration data.Affected if The tree.dat file exists in the CuteFTP installation or user data directory
-
Inspect tree.dat contents for stored passwordsOpen or examine the tree.dat file using a text editor or hex viewer. Look for patterns resembling FTP server addresses, usernames, and encrypted password strings stored in plain text or weak encryption format.Affected if The tree.dat file contains FTP server hostnames, usernames, or recognizable password data in encrypted or encoded form
-
Verify password storage feature is enabledCheck CuteFTP settings or site manager configuration. If sites have been added and saved with passwords stored, this feature was used. Review the Site Manager or connection profiles.Affected if User has saved FTP site configurations with stored passwords in CuteFTP Site Manager
A user is affected if CuteFTP version 2.x or earlier is installed, the tree.dat file exists, and it contains stored FTP credentials with weak encryption that could be recovered by a local attacker.
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 dataUsers should avoid storing passwords in CuteFTP and use alternative secure password management solutions; organizations should assess whether legacy CuteFTP installations with stored passwords still exist and revoke potentially compromised credentials.
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0084 — 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-2000-0084 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