# CVE-2004-1216: Denial of service in n/a

> Remote attackers can freeze the Kreed game server by sending long nicknames or model types, requiring manual intervention to resume.

- **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:** No
- **Published:** 15 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p6q5-476v-xhwv

## What is CVE-2004-1216?

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

### Official description

The scripts that handle players in Kreed 1.05 and earlier allow remote attackers to cause a denial of service (server freeze) via a long (1) nickname or (2) model type, which generates dialog boxes on the server that must be manually handled before the server continues the game.

## Which versions are affected by CVE-2004-1216?

It affects 1 product.


Products: Burut Kreed.

## How do I fix CVE-2004-1216?

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

## Is CVE-2004-1216 being exploited?

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

Public exploit code:

- Kreed 1.05 - Format String / Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1214](https://insights.sbomify.com/CVE-2004-1214/): Other in n/a (critical 10.0)
- [CVE-2004-1215](https://insights.sbomify.com/CVE-2004-1215/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1216 and fix it if it is affected.

What it is: CVE-2004-1216 is a medium-severity denial of service vulnerability in n/a, published on 15 Dec 2004. 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-2004-1216 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-2004-1216/ (Markdown: https://insights.sbomify.com/CVE-2004-1216/index.md)
```

## Sources

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

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