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

> Remote attackers can execute arbitrary code via a buffer overflow in the Gnome Batalla Naval game server.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0407, GHSA-qwjj-948r-x92x

## What is CVE-2003-0407?

CVE-2003-0407 is a critical memory corruption vulnerability in n/a, published on 11 Jun 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in gbnserver for Gnome Batalla Naval 1.0.4 allows remote attackers to execute arbitrary code via a long connection string.

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

It affects 1 product.


Products: Gnome Batalla Naval.

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

Upgrade to a fixed version.

## Is CVE-2003-0407 being exploited?

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

Public exploit code:

- Batalla Naval 1.0 4 - Remote Buffer Overflow (1) (exploitdb)
- Batalla Naval 1.0 4 - Remote Buffer Overflow (2) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0407 is a critical memory corruption vulnerability in n/a, published on 11 Jun 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0407 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-2003-0407/ (Markdown: https://insights.sbomify.com/CVE-2003-0407/index.md)
```

## Sources

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

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