# CVE-2002-1840: Hardcoded credentials in n/a

> A backdoor in the irssi IRC client configuration file allows remote attackers to access the system without authentication.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-c25w-grpg-cp6j

## What is CVE-2002-1840?

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

### Official description

irssi IRC client 0.8.4, when downloaded after 14-March-2002, could contain a backdoor in the configuration file, which allows remote attackers to access the system.

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

It affects 1 product.


Products: Irssi Irssi.

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

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

## Is CVE-2002-1840 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10965](https://insights.sbomify.com/CVE-2017-10965/): Null dereference in n/a (critical 9.8)
- [CVE-2017-10966](https://insights.sbomify.com/CVE-2017-10966/): Use after free in n/a (critical 9.8)
- [CVE-2017-7191](https://insights.sbomify.com/CVE-2017-7191/): Use after free in n/a (critical 9.8)
- [CVE-2007-4396](https://insights.sbomify.com/CVE-2007-4396/): Command injection in n/a (critical 9.3)
- [CVE-2019-13045](https://insights.sbomify.com/CVE-2019-13045/): Use after free in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1840 is a critical vulnerability in n/a, published on 28 Jun 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-1840 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-1840/ (Markdown: https://insights.sbomify.com/CVE-2002-1840/index.md)
```

## Sources

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

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