# CVE-2006-2236: Memory corruption in n/a

> Remote attackers can execute arbitrary commands via a buffer overflow in the Quake 3 Engine triggered by a long remapShader command.

- **Severity:** High 7.6 (`AV:N/AC:H/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:** Yes
- **Published:** 8 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2236, GHSA-rx4g-vhm6-f7vc

## What is CVE-2006-2236?

CVE-2006-2236 is a high-severity memory corruption vulnerability in n/a, published on 8 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the Quake 3 Engine, as used by (1) ET 2.60, (2) Return to Castle Wolfenstein 1.41, and (3) Quake III Arena 1.32b allows remote attackers to execute arbitrary commands via a long remapShader command.

## Which versions are affected by CVE-2006-2236?

It affects 4 products.


Products: Id Software Quake 3 Arena, Id Software Quake 3 Engine, Id Software Return to Castle Wolfenstein, Id Software Wolfenstein Enemy Territory.

## How do I fix CVE-2006-2236?

Apply the vendor's patch.

## Is CVE-2006-2236 being exploited?

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

Public exploit code:

- Quake 3 Engine 1.32b - 'R_RemapShader()' Remote Client Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0303](https://insights.sbomify.com/CVE-2000-0303/): Path traversal in n/a (medium 6.4)
- [CVE-2001-1289](https://insights.sbomify.com/CVE-2001-1289/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2236 and fix it if it is affected.

What it is: CVE-2006-2236 is a high-severity memory corruption vulnerability in n/a, published on 8 May 2006. 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-2006-2236 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-2006-2236/ (Markdown: https://insights.sbomify.com/CVE-2006-2236/index.md)
```

## Sources

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

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