# CVE-2003-0611: Memory corruption in n/a

> Local attackers can exploit buffer overflows in xtokkaetama to gain elevated privileges via malicious command-line arguments or environment variables.

- **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:** 1 Aug 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-356, GHSA-mp8h-4xq6-5jg7

## What is CVE-2003-0611?

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

### Official description

Multiple buffer overflows in xtokkaetama 1.0 allow local users to gain privileges via a long (1) -display command line argument or (2) XTOKKAETAMADIR environment variable.

## Which versions are affected by CVE-2003-0611?

It affects 1 product.


Products: Xtokkaetama Xtokkaetama.

## How do I fix CVE-2003-0611?

Apply the vendor's patch.

## Is CVE-2003-0611 being exploited?

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

Public exploit code:

- xtokkaetama 1.0b (RedHat 9.0) - Local Game (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0652](https://insights.sbomify.com/CVE-2003-0652/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0611 and fix it if it is affected.

What it is: CVE-2003-0611 is a medium-severity memory corruption vulnerability in n/a, published on 1 Aug 2003. 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-2003-0611 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-2003-0611/ (Markdown: https://insights.sbomify.com/CVE-2003-0611/index.md)
```

## Sources

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

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