# CVE-2005-3488: Denial of service in n/a

> Remote attackers can cause a denial of service in Scorched 3D by sending a negative player count that bypasses validation, hanging the server.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-3488, GHSA-m2vr-m45f-9w5x

## What is CVE-2005-3488?

CVE-2005-3488 is a high-severity denial of service vulnerability in n/a, published on 3 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Scorched 3D 39.1 (bf) and earlier allows remote attackers to cause a denial of service (long loop and server hang) via a negative numplayers value that bypasses a signed check in ServerConnectHandler.cpp.

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

It affects 1 product.


Products: Scorched 3d Scorched 3d.

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

Upgrade to a fixed version.

## Is CVE-2005-3488 being exploited?

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

Public exploit code:

- Scorched 3D 39.1 - Multiple Vulnerabilities (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-3486](https://insights.sbomify.com/CVE-2005-3486/): Memory corruption in n/a (high 7.5)
- [CVE-2005-3487](https://insights.sbomify.com/CVE-2005-3487/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3488 is a high-severity denial of service vulnerability in n/a, published on 3 Nov 2005. 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-2005-3488 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-3488/ (Markdown: https://insights.sbomify.com/CVE-2005-3488/index.md)
```

## Sources

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

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