# CVE-2002-1653: Weak cryptography in n/a

> Remote attackers can sniff sensitive data because Cryptcat server mode fails to enable encryption when started with the -e option.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1653, GHSA-rw3w-c7r4-m22q

## What is CVE-2002-1653?

CVE-2002-1653 is a medium-severity vulnerability in n/a, published on 28 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Farm9 Cryptcat, when started in server mode with the -e option, does not enable encryption, which allows clients to communicate without encryption despite intended configuration, and may allow remote attackers to sniff sensitive information.

## Which versions are affected by CVE-2002-1653?

It affects 1 product.


Products: Farm9 Cryptcat.

## How do I fix CVE-2002-1653?

No fix published yet.

## Is CVE-2002-1653 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1653 and fix it if it is affected.

What it is: CVE-2002-1653 is a medium-severity vulnerability in n/a, published on 28 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1653 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-2002-1653/ (Markdown: https://insights.sbomify.com/CVE-2002-1653/index.md)
```

## Sources

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

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