# CVE-2006-5982: Information disclosure in n/a

> Attackers can read plaintext passwords from the server directory, compromising user credentials in SeleniumServer FTP Server.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9hhm-m7cj-vc5h

## What is CVE-2006-5982?

CVE-2006-5982 is a critical vulnerability in n/a, published on 20 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SeleniumServer 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.

Weakness: CWE-310

## Which versions are affected by CVE-2006-5982?

It affects 1 product.


Products: Biba Software Seleniumserver Ftp Server.

## How do I fix CVE-2006-5982?

No fix has been published for CVE-2006-5982 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-5982 being exploited?

There is no known exploitation of CVE-2006-5982 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-5981](https://insights.sbomify.com/CVE-2006-5981/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5982 and fix it if it is affected.

What it is: CVE-2006-5982 is a critical vulnerability in n/a, published on 20 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5982 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-5982/ (Markdown: https://insights.sbomify.com/CVE-2006-5982/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-5982
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-5982
- OSV: https://osv.dev/vulnerability/CVE-2006-5982

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-5982/
Summaries are generated and may contain mistakes; the official description above is the record.