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

> Remote attackers can execute arbitrary code on Rogue Trooper and Prism game servers via a stack-based buffer overflow in the Asura engine.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 23 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wqjj-5gv3-62gc

## What is CVE-2007-4508?

CVE-2007-4508 is a medium-severity memory corruption vulnerability in n/a, published on 23 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in Rebellion Asura engine, as used for the server in Rogue Trooper 1.0 and earlier and Prism 1.1.1.0 and earlier, allows remote attackers to execute arbitrary code via a long string in a 0xf007 packet for the challenge B query.

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

It affects 2 products.


Products: Rebellion Rogue Trooper, Rival Interactive Prism.

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

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

## Is CVE-2007-4508 being exploited?

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

Public exploit code:

- Asura Engine Challenge B Query - Remote Stack Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4508 is a medium-severity memory corruption vulnerability in n/a, published on 23 Aug 2007. 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-2007-4508 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-2007-4508/ (Markdown: https://insights.sbomify.com/CVE-2007-4508/index.md)
```

## Sources

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

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