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

> Remote attackers can execute arbitrary code via buffer overflows in Medal of Honor games when playing on a Local Area Network.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f97q-pghf-w265

## What is CVE-2004-0735?

CVE-2004-0735 is a high-severity memory corruption vulnerability in n/a, published on 23 Jul 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Medal of Honor (1) Allied Assault 1.11v9 and earlier, (2) Breakthrough 2.40b and earlier, and (3) Spearhead 2.15 and earlier, when playing on a Local Area Network (LAN), allows remote attackers to execute arbitrary code via vectors such as (1) the getinfo query, (2) the connect packet, and other unknown vectors.

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

It affects 1 product.


Products: Electronic Arts Medal of Honor Allied Assault.

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

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

## Is CVE-2004-0735 being exploited?

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

Public exploit code:

- Medal of Honor Allied Assault getinfo Stack Buffer Overflow (metasploit)
- Medal of Honor - Remote Buffer Overflow (PoC) (exploitdb)
- Medal of Honor Spearhead (Linux) - Server Remote Buffer Overflow (exploitdb)
- Medal of Honor Allied Assault - getinfo Stack Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0735 is a high-severity memory corruption vulnerability in n/a, published on 23 Jul 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0735 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-0735/ (Markdown: https://insights.sbomify.com/CVE-2004-0735/index.md)
```

## Sources

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

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