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

> Weak XOR encryption allows local attackers to recover stored passwords and take over user accounts in Trillian.

- **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:** 16 Nov 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-89c4-g57m-vv8w

## What is CVE-2002-2162?

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

### Official description

Cerulean Studios Trillian 0.73 and earlier use weak encrypttion (XOR) for storing user passwords in .ini files in the Trillian directory, which allows local users to gain access to other user accounts.

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

It affects 1 product.


Products: Cerulean Studios Trillian.

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

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

## Is CVE-2002-2162 being exploited?

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

Public exploit code:

- Trillian Instant Messaging 0.x - Credential Encryption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5401](https://insights.sbomify.com/CVE-2008-5401/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-5402](https://insights.sbomify.com/CVE-2008-5402/): Use after free in n/a (critical 10.0)
- [CVE-2008-5403](https://insights.sbomify.com/CVE-2008-5403/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-2390](https://insights.sbomify.com/CVE-2002-2390/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2409](https://insights.sbomify.com/CVE-2008-2409/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2162 is a medium-severity vulnerability in n/a, published on 16 Nov 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-2002-2162 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-2002-2162/ (Markdown: https://insights.sbomify.com/CVE-2002-2162/index.md)
```

## Sources

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

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