# CVE-2007-6010: Denial of service in n/a

> Remote attackers can crash the Pioneers game server daemon via unspecified vectors, causing a denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6010, GHSA-mrhq-47wm-2m8c

## What is CVE-2007-6010?

CVE-2007-6010 is a high-severity denial of service vulnerability in n/a, published on 15 Nov 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in pioneers (formerly gnocatan) 0.11.3 allows remote attackers to cause a denial of service (daemon crash) via unspecified vectors that trigger an assert error.  NOTE: this issue reportedly exists because of an incomplete fix for CVE-2007-5933.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2007-6010?

It affects 1 product.


Products: Pioneers Pioneers.

## How do I fix CVE-2007-6010?

Upgrade to a fixed version.

## Is CVE-2007-6010 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5933](https://insights.sbomify.com/CVE-2007-5933/): Denial of service in n/a (high 7.8)
- [CVE-2006-0467](https://insights.sbomify.com/CVE-2006-0467/): Unspecified vulnerability in Pioneers (formerly gnocatan) before 0.9.49 allows remote attackers to cause a denial of service (application cr (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6010 and fix it if it is affected.

What it is: CVE-2007-6010 is a high-severity denial of service vulnerability in n/a, published on 15 Nov 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6010 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-2007-6010/ (Markdown: https://insights.sbomify.com/CVE-2007-6010/index.md)
```

## Sources

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

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