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

> Weak encryption in Hummingbird FTP allows attackers to recover stored passwords and gain unauthorized privileges.

- **Severity:** High 7.5 (`AV:N/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:** 17 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qxc4-hf32-x4jr

## What is CVE-2005-2599?

CVE-2005-2599 is a high-severity vulnerability in n/a, published on 17 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hummingbird FTP for Connectivity 10.0 uses weak encryption (trivial encoding) to store the user's password in the FTP profile, which allows attackers to gain privileges.

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

It affects 1 product.


Products: Hummingbird Connectivity.

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

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

## Is CVE-2005-2599 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1815](https://insights.sbomify.com/CVE-2005-1815/): Memory corruption in n/a (medium 5.0)
- [CVE-2004-2729](https://insights.sbomify.com/CVE-2004-2729/): Privilege escalation in n/a (medium 4.4)
- [CVE-2004-2728](https://insights.sbomify.com/CVE-2004-2728/): Memory corruption in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2599 is a high-severity vulnerability in n/a, published on 17 Aug 2005. 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-2005-2599 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-2005-2599/ (Markdown: https://insights.sbomify.com/CVE-2005-2599/index.md)
```

## Sources

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

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