# CVE-2002-1566: Denial of service in n/a

> Remote attackers can crash the netris game client by sending a long string to port 9284 when the wait option is enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1566, GHSA-8f4h-52c3-crrw

## What is CVE-2002-1566?

CVE-2002-1566 is a medium-severity denial of service vulnerability in n/a, published on 15 Aug 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

netris 0.5, and possibly other versions before 0.52, when running with the -w (wait) option, allows remote attackers to cause a denial of service (crash) via a long string to port 9284.

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

It affects 1 product.


Products: Netris Netris.

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

Upgrade to a fixed version.

## Is CVE-2002-1566 being exploited?

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

Public exploit code:

- Netris 0.3/0.4/0.5 - Remote Memory Corruption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0685](https://insights.sbomify.com/CVE-2003-0685/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1566 is a medium-severity denial of service vulnerability in n/a, published on 15 Aug 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1566 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-1566/ (Markdown: https://insights.sbomify.com/CVE-2002-1566/index.md)
```

## Sources

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

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