# CVE-2004-1500: Memory corruption in n/a

> Remote authenticated users can crash the Lithtech game engine via format string specifiers in nicknames or messages.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fg42-fgq3-gwpm

## What is CVE-2004-1500?

CVE-2004-1500 is a low-severity memory corruption vulnerability in n/a, published on 19 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Format string vulnerability in the Lithtech engine, as used in multiple games, allows remote authenticated users to cause a denial of service (application crash) via format string specifiers in (1) a nickname or (2) a message.

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

It affects 11 products.


Products: Freeform Interactive Purge Jihad, Monolith Productions Alien Versus Predator, Monolith Productions Blood, Monolith Productions Contract Jack, Monolith Productions Global Operations, Monolith Productions Kiss Psycho Circus, Monolith Productions Legends of Might and Magic, Monolith Productions No One Lives Forever, Monolith Productions Sanity, Monolith Productions Shogo, Monolith Productions Tron.

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

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

## Is CVE-2004-1500 being exploited?

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

Public exploit code:

- Monolith Lithtech Game Engine - Multiple Remote Format String Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1500 is a low-severity memory corruption vulnerability in n/a, published on 19 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1500 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-1500/ (Markdown: https://insights.sbomify.com/CVE-2004-1500/index.md)
```

## Sources

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

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