CVE-2006-5982
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 · uneditedSeleniumServer FTP Server 1.0, and possibly earlier, stores user passwords in plaintext in the Servers directory, which allows attackers to obtain passwords by reading the file. NOTE: the provenance of this information is unknown; details are obtained from third party sources.
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 confidenceSeleniumServer FTP Server 1.0 and earlier versions store user passwords in plaintext within the Servers directory on the file system. Any attacker with file system access—whether through another vulnerability, insider access, or system compromise—can directly read these plaintext passwords and impersonate users.
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= 1.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Identify installed Seleniumserver FTP Server versionCheck the program's version through its executable, installer, or installed files. Common locations include the program directory, Add/Remove Programs in Windows, or package management systems on Linux.Affected if The installed version is 1.0 or earlier (1.0 and earlier versions are affected)
-
Locate the Servers directoryFind the Servers directory within the Seleniumserver FTP Server installation folder. This is where user configuration and authentication data is stored.Affected if The Servers directory exists on the file system (prerequisite for the vulnerability to apply)
-
Identify password storage filesExamine files within the Servers directory for user account configuration or authentication data. Look for files that may contain user credentials or authentication settings.Affected if Files containing user credentials exist in the Servers directory
-
Inspect for plaintext passwordsOpen the credential files using a text editor or command to view their contents directly. Search for visible password strings in plain text format rather than hashed or encrypted values.Affected if User passwords are stored in plaintext (readable, unhashed, unencrypted format) within these files
If Seleniumserver FTP Server version 1.0 or earlier is installed and plaintext passwords are found in the Servers directory, the environment is affected by CVE-2006-5982.
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 dataReplace plaintext password storage with salted cryptographic hash functions (e.g., bcrypt, Argon2) and update the authentication logic to verify submitted passwords against the stored hashes. Existing plaintext passwords must be migrated to the new hashed format.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5982 — 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-2006-5982 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