# CVE-2004-1805: Other in n/a

> Remote attackers can cause crashes or execute arbitrary code via format string vulnerabilities in Unreal Engine class names.

- **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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-48p4-c835-2pjf

## What is CVE-2004-1805?

CVE-2004-1805 is a medium-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in games using the Epic Games Unreal Engine 436 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via format string specifiers in class names.

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

It affects 1 product.


Products: Epic Games Unreal Engine.

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

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

## Is CVE-2004-1805 being exploited?

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

Public exploit code:

- Epic Games Unreal Tournament Server 436.0 - Engine Remote Format String (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1432](https://insights.sbomify.com/CVE-2003-1432/): Epic Games Unreal Engine 226f through 436 allows remote attackers to cause a denial of service (CPU consumption or crash) and possibly execu (critical 10.0)
- [CVE-2003-1431](https://insights.sbomify.com/CVE-2003-1431/): Memory corruption in n/a (high 7.1)
- [CVE-2003-1430](https://insights.sbomify.com/CVE-2003-1430/): Path traversal in n/a (medium 5.0)
- [CVE-2007-4442](https://insights.sbomify.com/CVE-2007-4442/): Memory corruption in n/a (medium 5.0)
- [CVE-2007-4443](https://insights.sbomify.com/CVE-2007-4443/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1805 is a medium-severity vulnerability in n/a, published on 10 May 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-1805 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-1805/ (Markdown: https://insights.sbomify.com/CVE-2004-1805/index.md)
```

## Sources

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

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