# CVE-2004-1220: Null dereference in n/a

> A remote master server can crash the Battlefield 1942 or Vietnam client by sending a reply with an excessively large player count, causing a null dereference.

- **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:** 15 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q7fv-5v6x-mw8p

## What is CVE-2004-1220?

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

### Official description

Battlefield 1942 1.6.19 and earlier, and Battlefield Vietnam 1.2 and earlier, allows a remote master server to cause a denial of service (client crash) via a server reply that contains a large numplayers value, which triggers a null dereference.

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

It affects 2 products.


Products: Digital Illusions Battlefield 1942, Digital Illusions Battlefield Vietnam.

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

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

## Is CVE-2004-1220 being exploited?

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

Public exploit code:

- Battlefield 1942 1.6.19 + Vietnam 1.2 - Broadcast Client Crash (exploitdb)
- Battlefield (BFCC < 1.22_A /BFVCC < 2.14_B / BF2CC) - Authentication Bypass / Password Stealer / Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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