# CVE-2000-1175: Memory corruption in n/a

> Local attackers can execute arbitrary commands via a buffer overflow in the Koules game using long command line arguments.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3v35-rfwh-3mc8

## What is CVE-2000-1175?

CVE-2000-1175 is a high-severity memory corruption vulnerability in n/a, published on 19 Dec 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Koules 1.4 allows local users to execute arbitrary commands via a long command line argument.

## Which versions are affected by CVE-2000-1175?

It affects 1 product.


Products: Jan Hubicka Koules.

## How do I fix CVE-2000-1175?

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

## Is CVE-2000-1175 being exploited?

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

Public exploit code:

- Jan Hubicka Koules 1.4 - 'Svgalib' Local Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-1175 and fix it if it is affected.

What it is: CVE-2000-1175 is a high-severity memory corruption vulnerability in n/a, published on 19 Dec 2000. 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-2000-1175 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-2000-1175/ (Markdown: https://insights.sbomify.com/CVE-2000-1175/index.md)
```

## Sources

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

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