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

> Remote attackers can cause a denial of service in games using the Lithtech engine by sending specific UDP packets that crash the listening loop.

- **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:** 12 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-62mf-43pr-p6gj

## What is CVE-2004-1395?

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

### Official description

The Lithtech engine, as used in (1) Contract Jack 1.1 and earlier, (2) No one lives forever 2 1.3 and earlier, (3) Tron 2.0 1.042 and earlier, (4) F.E.A.R. (First Encounter Assault and Recon), and possibly other games, allows remote attackers to cause a denial of service (connection refused) via a UDP packet that causes recvfrom to generate a return code that causes the listening loop to exit, as demonstrated using zero byte packets or packets between 8193 and 12280 bytes, which result in conditions that are not "Operation would block."

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

It affects 3 products.


Products: Monolith Productions Contract Jack, Monolith Productions No One Lives Forever 2, Monolith Productions Tron.

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

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

## Is CVE-2004-1395 being exploited?

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

Public exploit code:

- Lithtech Engine (new protocol) - Socket Unreacheable Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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