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

> Local attackers can exploit buffer overflows in xsok to execute arbitrary code and gain elevated 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:** No
- **Published:** 22 Jan 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jggx-7jmp-p9ff

## What is CVE-2004-0074?

CVE-2004-0074 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jan 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 xsok 1.02 allows local users to gain privileges via (1) a long LANG environment variable, or (2) a long -xsokdir command line argument, a different vulnerability than CVE-2003-0949.

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

It affects 1 product.


Products: Michael Bischoff Xsok.

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

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

## Is CVE-2004-0074 being exploited?

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

Public exploit code:

- XSOK 1.0 2 - 'LANG Environment' Local Buffer Overrun (exploitdb)
- XSOK 1.02 - '-xsokdir' Local Buffer Overflow Game (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0949](https://insights.sbomify.com/CVE-2003-0949/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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