# CVE-2006-2393: Denial of service in n/a

> Remote attackers can crash the Empire IRC server by sending long text strings, causing a denial of service.

- **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:** 16 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mmw4-j4cf-332c

## What is CVE-2006-2393?

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

### Official description

The client_cmd function in Empire 4.3.2 and earlier allows remote attackers to cause a denial of service (application crash) by causing long text strings to be appended to the player->client buffer, which causes an invalid memory access.

## Which versions are affected by CVE-2006-2393?

It affects 1 product.


Products: Empire Server Empire Server.

## How do I fix CVE-2006-2393?

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

## Is CVE-2006-2393 being exploited?

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

Public exploit code:

- Empire 4.3.2 - 'strncat' Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3169](https://insights.sbomify.com/CVE-2008-3169/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-1840](https://insights.sbomify.com/CVE-2006-1840/): Other in n/a (medium 6.4)
- [CVE-2008-3168](https://insights.sbomify.com/CVE-2008-3168/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2393 and fix it if it is affected.

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

## Sources

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

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