# CVE-1999-0972: Memory corruption in n/a

> A buffer overflow in the Xshipwars game allows attackers to execute arbitrary code, posing a risk to users running this legacy X11 application.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 4 Jan 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-vc2w-gc8v-3rfp

## What is CVE-1999-0972?

CVE-1999-0972 is a high-severity memory corruption vulnerability in n/a, published on 4 Jan 2000. 

### Official description

Buffer overflow in Xshipwars xsw program.

## Which versions are affected by CVE-1999-0972?

It affects 1 product.


Products: Wolfpack Development Xshipwars.

## How do I fix CVE-1999-0972?

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

## Is CVE-1999-0972 being exploited?

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

Public exploit code:

- WolfPack Development XSHIPWARS 1.0/1.2.4 - Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0972 and fix it if it is affected.

What it is: CVE-1999-0972 is a high-severity memory corruption vulnerability in n/a, published on 4 Jan 2000. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0972 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-1999-0972/ (Markdown: https://insights.sbomify.com/CVE-1999-0972/index.md)
```

## Sources

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

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