# CVE-2008-3410: Null dereference in n/a

> Remote attackers can crash the Unreal Tournament 3 server by sending a malformed UDP packet with an invalid size field.

- **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:** 31 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jm34-m4qh-33mq

## What is CVE-2008-3410?

CVE-2008-3410 is a medium-severity vulnerability in n/a, published on 31 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unreal Tournament 3 1.3beta4 and earlier allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a UDP packet in which the value of a certain size field is greater than the total packet length, aka attack 2 in ut3mendo.c.

Weakness: CWE-399, CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Epic Games Unreal Tournament 3.

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

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

## Is CVE-2008-3410 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4243](https://insights.sbomify.com/CVE-2008-4243/): Path traversal in n/a (high 7.8)
- [CVE-2008-3409](https://insights.sbomify.com/CVE-2008-3409/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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