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

> Local attackers can execute arbitrary code and gain privileges by providing long command-line arguments to the MAME emulator.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gwh2-2hj8-48gr

## What is CVE-2006-0176?

CVE-2006-0176 is a high-severity memory corruption vulnerability in n/a, published on 11 Jan 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in certain functions in src/fileio.c and src/unix/fileio.c in xmame before 11 January 2006 may allow local users to gain privileges via a long (1) -lang, (2) -ctrlr, (3) -pb, or (4) -rec argument on many operating systems, and via a long (5) -jdev argument on Ubuntu Linux.

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

It affects 1 product.


Products: Xmame Xmame.

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

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

## Is CVE-2006-0176 being exploited?

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

Public exploit code:

- Xmame 0.102 - '-lang' Local Buffer Overflow (exploitdb)
- Xmame 0.102 - 'lang' Local Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0176 is a high-severity memory corruption vulnerability in n/a, published on 11 Jan 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0176 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-0176/ (Markdown: https://insights.sbomify.com/CVE-2006-0176/index.md)
```

## Sources

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

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