# CVE-2002-0425: Information disclosure in n/a

> Remote attackers can leak sensitive alternate IRC nicknames from mIRC clients via a specific DCC connection request that users cannot cancel.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fqrq-528h-rhwq

## What is CVE-2002-0425?

CVE-2002-0425 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

mIRC DCC server protocol allows remote attackers to gain sensitive information such as alternate IRC nicknames via a "100 testing" message in a DCC connection request that cannot be ignored or canceled by the user, which may leak the alternate nickname in a response message.

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

It affects 1 product.


Products: Khaled Mardam-Bey Mirc.

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

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

## Is CVE-2002-0425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1456](https://insights.sbomify.com/CVE-2002-1456/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0231](https://insights.sbomify.com/CVE-2002-0231/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0315](https://insights.sbomify.com/CVE-2001-0315/): Security feature bypass in n/a (high 7.5)
- [CVE-1999-0399](https://insights.sbomify.com/CVE-1999-0399/): Path traversal in n/a (high 7.5)
- [CVE-2001-0944](https://insights.sbomify.com/CVE-2001-0944/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0425 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-0425 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-0425/ (Markdown: https://insights.sbomify.com/CVE-2002-0425/index.md)
```

## Sources

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

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