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

> Local attackers can execute arbitrary code via a buffer overflow in the high score file of the zblast game.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2003
- **Updated:** 17 Sep 2024
- **Also known as:** DSA-369, GHSA-g25v-xm4w-5pqf

## What is CVE-2003-0613?

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

### Official description

Buffer overflow in zblast-svgalib of zblast 1.2.1 and earlier allows local users to execute arbitrary code via the high score file.

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

It affects 1 product.


Products: Zblast Zblast.

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

Apply the vendor's patch.

## Is CVE-2003-0613 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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