# CVE-2005-2898: Weak cryptography in n/a

> Local attackers can recover stored passwords if secure mode is disabled due to weak encryption in FileZilla configuration files.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 14 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-927p-j9gg-9h8q

## What is CVE-2005-2898?

CVE-2005-2898 is a medium-severity vulnerability in n/a, published on 14 Sep 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NOTE: this issue has been disputed by the vendor.  FileZilla 2.2.14b and 2.2.15, and possibly earlier versions, when "Use secure mode" is disabled, uses a weak encryption scheme to store the user's password in the configuration settings file, which allows local users to obtain sensitive information.  NOTE: the vendor has disputed the issue, stating that "the problem is not a vulnerability at all, but in fact a fundamental issue of every single program that can store passwords transparently.

## Which versions are affected by CVE-2005-2898?

It affects 1 product.


Products: Filezilla Filezilla.

## How do I fix CVE-2005-2898?

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

## Is CVE-2005-2898 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2898 exists.

Public exploit code:

- FileZilla 2.2.15 - FTP Client Hard-Coded Cipher Key (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2318](https://insights.sbomify.com/CVE-2007-2318/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0315](https://insights.sbomify.com/CVE-2007-0315/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0317](https://insights.sbomify.com/CVE-2007-0317/): Other in n/a (high 7.5)
- [CVE-2006-2403](https://insights.sbomify.com/CVE-2006-2403/): Memory corruption in n/a (high 7.5)
- [CVE-2006-6564](https://insights.sbomify.com/CVE-2006-6564/): Null dereference in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2898 and fix it if it is affected.

What it is: CVE-2005-2898 is a medium-severity vulnerability in n/a, published on 14 Sep 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2898 exists.

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-2005-2898/ (Markdown: https://insights.sbomify.com/CVE-2005-2898/index.md)
```

## Sources

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

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