# CVE-2008-7011: Denial of service in n/a

> Remote authenticated users can crash Unreal Engine game servers by triggering an assertion failure through multiple file downloads.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/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 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f3rf-78w5-mwvx

## What is CVE-2008-7011?

CVE-2008-7011 is a medium-severity denial of service vulnerability in n/a, published on 19 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Unreal engine, as used in Unreal Tournament 3 1.3, Unreal Tournament 2003 and 2004, Dead Man's Hand, Pariah, WarPath, Postal2, and Shadow Ops, allows remote authenticated users to cause a denial of service (server exit) via multiple file downloads from the server, which triggers an assertion failure when the Closing flag in UnChan.cpp is set.

Weakness: CWE-399

## Which versions are affected by CVE-2008-7011?

It affects 6 products.


Products: Digital Extreme Pariah, Epic Games Unreal Tournament, Groove Games Warpath, Human Head Studios Dead Mans Hand, Red Mercury Shadow Ops, Whiptail Interactive Postal.

## How do I fix CVE-2008-7011?

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

## Is CVE-2008-7011 being exploited?

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

Public exploit code:

- Unreal Engine - 'UnChan.cpp' Failed Assertion Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7011 and fix it if it is affected.

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

## Sources

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

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