# CVE-2005-0330: Memory corruption in n/a

> Remote authenticated users can trigger a buffer overflow via a long CD-key hash, potentially executing arbitrary code or causing denial of service.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5gmf-qpg2-cw88

## What is CVE-2005-0330?

CVE-2005-0330 is a low-severity memory corruption vulnerability in n/a, published on 10 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Painkiller 1.35 and earlier, and possibly other versions before 1.61, allows remote authenticated users to cause a denial of service and possibly execute arbitrary code via a long cd-key hash.

## Which versions are affected by CVE-2005-0330?

It affects 1 product.


Products: People Can Fly Painkiller.

## How do I fix CVE-2005-0330?

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

## Is CVE-2005-0330 being exploited?

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

Public exploit code:

- Painkiller 1.35 - in-game cd-key alpha-numeric Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1745](https://insights.sbomify.com/CVE-2004-1745/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0330 and fix it if it is affected.

What it is: CVE-2005-0330 is a low-severity memory corruption vulnerability in n/a, published on 10 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0330 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-2005-0330/ (Markdown: https://insights.sbomify.com/CVE-2005-0330/index.md)
```

## Sources

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

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