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

> Local users with games group membership can gain privileges by modifying score files to execute arbitrary code when another user plays tetris-bsd.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1539, GHSA-fqx7-q9qr-3rrm

## What is CVE-2006-1539?

CVE-2006-1539 is a high-severity memory corruption vulnerability in n/a, published on 30 Mar 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

Multiple buffer overflows in the checkscores function in scores.c in tetris-bsd in bsd-games before 2.17-r1 in Gentoo Linux might allow local users with games group membership to gain privileges by modifying tetris-bsd.scores to contain crafted executable content, which is executed when another user launches tetris-bsd.

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

It affects 1 product.


Products: Bsd-Games Tetris-Bsd.

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

Upgrade to a fixed version.

## Is CVE-2006-1539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1539 is a high-severity memory corruption vulnerability in n/a, published on 30 Mar 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: There is no known exploitation of CVE-2006-1539 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-2006-1539/ (Markdown: https://insights.sbomify.com/CVE-2006-1539/index.md)
```

## Sources

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

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