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

> Local attackers can exploit buffer overflows in xboing to gain elevated privileges on the system.

- **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:** 25 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-451, GHSA-x3r4-63h4-jwvq

## What is CVE-2004-0149?

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

### Official description

Multiple buffer overflows in xboing before 2.4 allow local users to gain privileges.

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

It affects 1 product.


Products: Xboing Xboing.

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

Upgrade to a fixed version.

## Is CVE-2004-0149 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0149 is a medium-severity memory corruption vulnerability in n/a, published on 25 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0149 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-2004-0149/ (Markdown: https://insights.sbomify.com/CVE-2004-0149/index.md)
```

## Sources

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

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