# CVE-2004-2340: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via login fields in PunkBuster Screenshot Database Alpha 6, though the report's accuracy is disputed.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-79rf-5qc8-xrp9

## What is CVE-2004-2340?

CVE-2004-2340 is a high-severity SQL injection vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

** UNVERIFIABLE **  SQL injection vulnerability in PunkBuster Screenshot Database (PB-DB) Alpha 6 allows remote attackers to execute arbitrary SQL commands via the username and password fields of the login form.  NOTE: the original vulnerability report contains several significant inconsistencies that make it unclear whether the report is accurate, including (1) PB-DB is really the "PunkBuster Screenshot Database" and not "PunkBuster" itself; (2) there is no apparent association between PunkBuster and "Punky Brewster"; (3) the claimed source code is not anywhere in Alpha 6.

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

It affects 1 product.


Products: Even Balance Punkbuster Database.

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

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

## Is CVE-2004-2340 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2340 is a high-severity SQL injection vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2340 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-2004-2340/ (Markdown: https://insights.sbomify.com/CVE-2004-2340/index.md)
```

## Sources

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

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