# CVE-2004-0158: Memory corruption in n/a

> Local attackers can exploit a buffer overflow in lbreakout2 via a large HOME variable to gain games group privileges.

- **Severity:** Medium 4.6 (`AV:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0158, DSA-445, GHSA-jvqp-w76h-93jf

## What is CVE-2004-0158?

CVE-2004-0158 is a medium-severity memory corruption vulnerability in n/a, published on 10 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in lbreakout2 allows local users to gain 'games' group privileges via a large HOME environment variable to (1) editor.c, (2) theme.c, (3) manager.c, (4) config.c, (5) game.c, (6) levels.c, or (7) main.c.

## Which versions are affected by CVE-2004-0158?

It affects 1 product.


Products: Lgames Lbreakout2.

## How do I fix CVE-2004-0158?

Apply the vendor's patch.

## Is CVE-2004-0158 being exploited?

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

Public exploit code:

- LGames LBreakout2 2.2.2 - Multiple Environment Variable Buffer Overflow Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0158 and fix it if it is affected.

What it is: CVE-2004-0158 is a medium-severity memory corruption vulnerability in n/a, published on 10 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0158 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-2004-0158/ (Markdown: https://insights.sbomify.com/CVE-2004-0158/index.md)
```

## Sources

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

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