# CVE-2010-2702: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in Unreal Engine games when downloads are enabled.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rgx2-hj64-5vc5

## What is CVE-2010-2702?

CVE-2010-2702 is a critical memory corruption vulnerability in n/a, published on 12 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the UGameEngine::UpdateConnectingMessage function in the Unreal engine 1, 2, and 2.5, as used in multiple games including Unreal Tournament 2004, Unreal tournament 2003, Postal 2, Raven Shield, and SWAT4, when downloads are enabled, allows remote attackers to execute arbitrary code via a long LEVEL field in a WELCOME response to a download request.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-2702?

It affects 6 products.


Products: Epicgames Postal 2, Epicgames Raven Shield, Epicgames Swat 4, Epicgames Unreal Engine, Epicgames Unreal Tournament 2003, Epicgames Unreal Tournament 2004.

## How do I fix CVE-2010-2702?

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

## Is CVE-2010-2702 being exploited?

There is no known exploitation of CVE-2010-2702 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2702 and fix it if it is affected.

What it is: CVE-2010-2702 is a critical memory corruption vulnerability in n/a, published on 12 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2702 in the wild and no public exploit code.

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-2010-2702/ (Markdown: https://insights.sbomify.com/CVE-2010-2702/index.md)
```

## Sources

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

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