# CVE-2007-5247: Memory corruption in n/a

> Remote attackers can execute arbitrary code or crash the game via format string vulnerabilities in Punkbuster packets when 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:** 6 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9mw5-93p4-vpwg

## What is CVE-2007-5247?

CVE-2007-5247 is a critical memory corruption vulnerability in n/a, published on 6 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple format string vulnerabilities in the Monolith Lithtech engine, as used by First Encounter Assault Recon (F.E.A.R.) 1.08 and earlier, when Punkbuster (PB) is enabled, allow remote attackers to execute arbitrary code or cause a denial of service (daemon crash) via format string specifiers in (1) a PB_Y packet to the YPG server on UDP port 27888 or (2) a PB_U packet to UCON on UDP port 27888, different vectors than CVE-2004-1500.  NOTE: this issue might be in Punkbuster itself, but there are insufficient details to be certain.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2007-5247?

It affects 1 product.


Products: Monolith Productions First Encounter Assault Recon.

## How do I fix CVE-2007-5247?

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

## Is CVE-2007-5247 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5247 and fix it if it is affected.

What it is: CVE-2007-5247 is a critical memory corruption vulnerability in n/a, published on 6 Oct 2007. 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-2007-5247 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-2007-5247/ (Markdown: https://insights.sbomify.com/CVE-2007-5247/index.md)
```

## Sources

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

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